From: James Bottomley <James.Bottomley@SteelEye.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
Ashutosh Naik <ashutosh.naik@gmail.com>,
support@qlogic.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] Re: [PATCH] scsi - Fix Broken Qlogic ISP2x00 Device Driver
Date: Wed, 02 Nov 2005 10:57:39 -0800 [thread overview]
Message-ID: <1130957859.3259.1.camel@mulgrave> (raw)
In-Reply-To: <20051102082142.GW5856@shell0.pdx.osdl.net>
On Wed, 2005-11-02 at 00:21 -0800, Chris Wright wrote:
> * Andrew Vasquez (andrew.vasquez@qlogic.com) wrote:
> > On Wed, 02 Nov 2005, Ashutosh Naik wrote:
> >
> > > This patch fixes the fact that although the scsi_transport_fc.h header
> > > file is not included in qla_def.h, we still reference the function
> > > fc_remote_port_unlock in the qlogic ISP2x00 device driver ,
> > > qla2xxx/qla_rscn.c
> >
> > Perhaps for the stable tree (2.6.14.x) this fix is appropriate. The
> > scsi-misc-2.6.git tree already has codes which address this issue.
>
> It's preferable to have that fix pending in scsi-misc for -stable.
This is the fix that's queued in scsi-misc for this:
http://www.kernel.org/git/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=aa353de649f1ba05a71b2f5b8eb1e99632ab54eb
But since this is only a compile warning, does it really warrant fixing
in the stable tree?
James
prev parent reply other threads:[~2005-11-02 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 7:13 [PATCH] scsi - Fix Broken Qlogic ISP2x00 Device Driver Ashutosh Naik
2005-11-02 8:07 ` Andrew Vasquez
2005-11-02 8:21 ` [stable] " Chris Wright
2005-11-02 18:47 ` Andrew Vasquez
2005-11-05 4:56 ` Ashutosh Naik
2005-11-02 18:57 ` James Bottomley [this message]
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=1130957859.3259.1.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=andrew.vasquez@qlogic.com \
--cc=ashutosh.naik@gmail.com \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@kernel.org \
--cc=support@qlogic.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