From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: Linux SCSI Mailing List <linux-scsi@vger.kernel.org>,
Seokmann Ju <seokmann.ju@qlogic.com>
Subject: Re: [PATCH 0/10] qla2xxx: updates for 2.6.26 [8.02.01-k2].
Date: Thu, 24 Apr 2008 17:51:56 -0500 [thread overview]
Message-ID: <1209077516.3121.31.camel@localhost.localdomain> (raw)
In-Reply-To: <20080424223736.GE4359@n8027av35btxc1.qlogic.org>
On Thu, 2008-04-24 at 15:37 -0700, Andrew Vasquez wrote:
> On Thu, 24 Apr 2008, James Bottomley wrote:
> > On Thu, 2008-04-24 at 15:19 -0700, Andrew Vasquez wrote:
> > > This patchset contains fixes/updates for 2.6.26.
[...]
> > So, since I have to guess, I put my money on:
> >
> > [PATCH 09/10] qla2xxx: Correct regression in relogin code
> >
> > needs backporting to stable to fix the 2.6.24 regression bug 10486.
> >
> > Do I win?
>
> Sure do. Send me your RTN and I'll wire you 10 million USD...
>
> All kidding aside, I've just sent the patch to stable@kernel.org for
> inclusion.
Unfortunately, that won't quit work. Stable won't accept a patch until
it's upstream. For that reason, I tag all such patches with
Cc: Stable Tree <stable@kernel.org>
in my git tree. This triggers an automatic email prod to the stable
team when the patch goes upstream, so unless the backport is non
trivial, that's all that's all that's needed.
I just needed to know where to put the tag.
James
next prev parent reply other threads:[~2008-04-24 22:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 22:19 [PATCH 0/10] qla2xxx: updates for 2.6.26 [8.02.01-k2] Andrew Vasquez
2008-04-24 22:21 ` [PATCH 01/10] qla2xxx: Collapse RISC-RAM retrieval code during a firmware-dump Andrew Vasquez
2008-04-24 22:21 ` [PATCH 02/10] qla2xxx: Wakeup DPC thread to process any deferred-work requests Andrew Vasquez
2008-04-24 22:21 ` [PATCH 03/10] qla2xxx: Correct ISP84XX verify-chip response handling Andrew Vasquez
2008-04-24 22:21 ` [PATCH 04/10] qla2xxx: Correct SRB usage-after-completion/free issues Andrew Vasquez
2008-04-24 22:21 ` [PATCH 05/10] qla2xxx: Re-register FDMI information after a LIP Andrew Vasquez
2008-04-24 22:21 ` [PATCH 06/10] qla2xxx: qla_os.c, make 2 functions static Andrew Vasquez
2008-04-24 22:21 ` [PATCH 07/10] qla2xxx: make qla2x00_issue_iocb_timeout() static Andrew Vasquez
2008-04-24 22:21 ` [PATCH 08/10] qla2xxx: Correct misc. endian and byte-ordering issues Andrew Vasquez
2008-04-24 22:21 ` [PATCH 09/10] qla2xxx: Correct regression in relogin code Andrew Vasquez
2008-04-24 22:21 ` [PATCH 10/10] qla2xxx: Update version number to 8.02.01-k2 Andrew Vasquez
2008-04-24 22:31 ` [PATCH 0/10] qla2xxx: updates for 2.6.26 [8.02.01-k2] James Bottomley
2008-04-24 22:37 ` Andrew Vasquez
2008-04-24 22:51 ` James Bottomley [this message]
2008-04-24 22:58 ` 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=1209077516.3121.31.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=seokmann.ju@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.