From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] SCSI fixes for 2.6.25-rc8
Date: Wed, 02 Apr 2008 21:05:48 +0300 [thread overview]
Message-ID: <47F3CAFC.2050401@panasas.com> (raw)
In-Reply-To: <1207082197.3100.26.camel@localhost.localdomain>
On Tue, Apr 01 2008 at 23:36 +0300, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> This patch constitutes three bug fixes (the reversion of the BSG queue
> fix is the most serious; without it we're getting eventual corruption in
> systems). The other two fix error legs or misleading reporting. The
> remaining 8 patches are all updates to the mvsas driver which was a late
> addition at the -rc1 phase, so while they're not truly bug fixes, they
> are enhancements to make that unreleased driver more roubust for 2.6.25.
>
> The patch is here:
>
> master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git
>
> The short changelog is:
>
> James Bottomley (2):
> libsas: Warn if ATA device detected but CONFIG_SCSI_SAS_ATA not set
> Revert " fix bsg queue oops with iscsi logout"
>
<snip>
Does this mean that we still have the iscsi logout bug if used from bsg
in 2.6.25 kernel? I just want to know what are the out-of-tree patches
I will need. Will the proper fix be candidate for the stable releases
of 2.6.25?
Thanks
Boaz
next prev parent reply other threads:[~2008-04-02 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 20:36 [GIT PATCH] SCSI fixes for 2.6.25-rc8 James Bottomley
2008-04-02 18:05 ` Boaz Harrosh [this message]
2008-04-02 18:16 ` James Bottomley
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=47F3CAFC.2050401@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.