From: James Smart <james.smart@emulex.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: "linux-scsi@vger.kernel.org" <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 13:20:22 -0500 [thread overview]
Message-ID: <4D5C1566.1040307@emulex.com> (raw)
In-Reply-To: <1297879459.3014.200.camel@mulgrave.site>
next merge window is fine. As for stable@kernel.org - probably.
-- james s
On 2/16/2011 1:04 PM, James Bottomley wrote:
> 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
>
>
prev parent reply other threads:[~2011-02-16 18:20 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
2011-02-16 18:20 ` James Smart [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=4D5C1566.1040307@emulex.com \
--to=james.smart@emulex.com \
--cc=James.Bottomley@suse.de \
--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