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:31:50 -0500 [thread overview]
Message-ID: <1209076310.3121.26.camel@localhost.localdomain> (raw)
In-Reply-To: <20080424221945.GC4359@n8027av35btxc1.qlogic.org>
On Thu, 2008-04-24 at 15:19 -0700, Andrew Vasquez wrote:
> This patchset contains fixes/updates for 2.6.26.
>
> drivers/scsi/qla2xxx/qla_dbg.c | 394 +++++++++++++-----------------------
> drivers/scsi/qla2xxx/qla_fw.h | 26 +--
> drivers/scsi/qla2xxx/qla_gbl.h | 4 -
> drivers/scsi/qla2xxx/qla_gs.c | 4 +-
> drivers/scsi/qla2xxx/qla_init.c | 2 +-
> drivers/scsi/qla2xxx/qla_isr.c | 4 +-
> drivers/scsi/qla2xxx/qla_mbx.c | 19 +-
> drivers/scsi/qla2xxx/qla_os.c | 12 +-
> drivers/scsi/qla2xxx/qla_version.h | 2 +-
> 9 files changed, 170 insertions(+), 297 deletions(-)
>
> here's the commits:
>
> - Collapse RISC-RAM retrieval code during a firmware-dump.
> - Wakeup DPC thread to process any deferred-work requests.
> - Correct ISP84XX verify-chip response handling.
> - Correct SRB usage-after-completion/free issues.
> - Re-register FDMI information after a LIP.
> - qla_os.c, make 2 functions static
> - make qla2x00_issue_iocb_timeout() static
> - Correct misc. endian and byte-ordering issues.
> - Correct regression in relogin code.
> - Update version number to 8.02.01-k2.
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?
James
next prev parent reply other threads:[~2008-04-24 22:31 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 ` James Bottomley [this message]
2008-04-24 22:37 ` [PATCH 0/10] qla2xxx: updates for 2.6.26 [8.02.01-k2] Andrew Vasquez
2008-04-24 22:51 ` James Bottomley
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=1209076310.3121.26.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox