From: Christoph Hellwig <hch@infradead.org>
To: Tomasz K?oczko <kloczek@rudy.mif.pg.gda.pl>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Chris Wright <chrisw@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Q: qla23xxx and lpfc (Was: Re: [GIT PATCH] SCSI updates for 2.6.12)
Date: Mon, 20 Jun 2005 11:45:44 +0100 [thread overview]
Message-ID: <20050620104544.GA28488@infradead.org> (raw)
In-Reply-To: <Pine.BSO.4.62.0506201217410.19853@rudy.mif.pg.gda.pl>
On Mon, Jun 20, 2005 at 12:33:49PM +0200, Tomasz K?oczko wrote:
> Included in vanilla 2.6.12 qla23xxx 8.00.02b5 is for me unuseable (fails
> on scaning luns and oopses on array controler reset) on x86_64 with
> qla2300 and for me works only version 8.01.00b2.
> Is it will be possible include this version in official tree ?
As said above a bad patch from Qlogic went in and Linus didn't pull the
release critical fixes tree before release. It'll be fixed in 2.6.12.1.
8.01.00b2 is full of crap and despite the higher version number actually
a regression vs the kernel driver in various aspects.
> Also is it will be possible include Emulex lpfc driver to official tree ?
See drivers/scsi/lpfc/
next prev parent reply other threads:[~2005-06-20 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 14:06 [GIT PATCH] SCSI updates for 2.6.12 James Bottomley
2005-06-18 14:16 ` Christoph Hellwig
2005-06-18 17:45 ` Chris Wright
2005-06-20 9:35 ` James Bottomley
2005-06-20 10:33 ` Q: qla23xxx and lpfc (Was: Re: [GIT PATCH] SCSI updates for 2.6.12) Tomasz Kłoczko
2005-06-20 10:45 ` Christoph Hellwig [this message]
2005-06-20 17:52 ` [GIT PATCH] SCSI updates for 2.6.12 Chris Wright
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050620104544.GA28488@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=kloczek@rudy.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox