From: Andrew Morton <akpm@osdl.org>
To: "Michael W. Shaffer" <mwshaffer@yahoo.com>
Cc: James.Bottomley@steeleye.com, andrew.vasquez@qlogic.com,
linux-scsi@vger.kernel.org
Subject: Re: [patch] Have qla2xxx driver bind fcports.
Date: Mon, 19 Jan 2004 13:49:44 -0800 [thread overview]
Message-ID: <20040119134944.515440b0.akpm@osdl.org> (raw)
In-Reply-To: <20040119214030.78010.qmail@web10408.mail.yahoo.com>
"Michael W. Shaffer" <mwshaffer@yahoo.com> wrote:
>
> > As far as the resync goes, I'd like to wait a while just to
> > see if any more bugs turn up in the ioctl/failover separation
> > piece ... it will be easier to debug if we have fewer changes,
> > so how does early 2.6.2 sound for this (depending, of course,
> > on when that actually is)?
>
> Thanks to everyone for figuring this out so quickly. Should I
> assume that this fix will be merged into 2.6.1-mm5 or so, and
> eventually into 2.6.2? I'll probably continue to do some beta
> testing on this system with the patches I have now, but I
> would most likely wait until the LUN fix is into the -mm tree
> before trying to move into production with it.
>
I added Andrew's patch to -mm. I'll get -mm5 out today.
James is suggesting 2.6.3-pre for merging this patch. That may be
conservative: we've only just started in on the post-2.6.1 work, so 2.6.2
is a while off yet.
next prev parent reply other threads:[~2004-01-19 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 17:03 [patch] Have qla2xxx driver bind fcports Andrew Vasquez
2004-01-19 17:11 ` James Bottomley
2004-01-19 21:40 ` Michael W. Shaffer
2004-01-19 21:49 ` Andrew Morton [this message]
2004-01-19 22:00 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2004-01-19 17:20 Andrew Vasquez
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=20040119134944.515440b0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=James.Bottomley@steeleye.com \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mwshaffer@yahoo.com \
/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