From: James Bottomley <James.Bottomley@suse.de>
To: james.smart@emulex.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/6] lpfc 8.3.21: Update lpfc to revision 8.3.21
Date: Wed, 16 Feb 2011 12:04:19 -0600 [thread overview]
Message-ID: <1297879459.3014.200.camel@mulgrave.site> (raw)
In-Reply-To: <1297877936.1492.19.camel@wookie>
On Wed, 2011-02-16 at 12:38 -0500, James Smart wrote:
> This patch set updates the lpfc driver to revision 8.3.21
>
> The patches for 8.3.21. contain:
>
> - Critical Errors and Bug Fixes
> - RRQ Implementation fixes.
> - FC Discovery changes.
> - Initialization and user interface changes.
> - Debugfs additions.
> - Change lpfc driver version to 8.3.21.
>
> The bugfixes were cut against scsi-misc-2.6
So I'll apply them agains the scsi-misc tree for the next merge window,
but would a cc: stable@kernel.org tag be appropriate? As in will they
apply on their own to the stable tree once upstream?
James
next prev parent reply other threads:[~2011-02-16 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 17:38 [PATCH 0/6] lpfc 8.3.21: Update lpfc to revision 8.3.21 James Smart
2011-02-16 18:04 ` James Bottomley [this message]
2011-02-16 18:20 ` James Smart
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=1297879459.3014.200.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.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