From: James Bottomley <James.Bottomley@SteelEye.com>
To: brking@us.ibm.com
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [GIT PATCH] SCSI bug fixes for 2.6.16-rc1
Date: Tue, 31 Jan 2006 17:09:50 -0600 [thread overview]
Message-ID: <1138748990.3307.33.camel@mulgrave> (raw)
In-Reply-To: <43DFD316.3080100@us.ibm.com>
On Tue, 2006-01-31 at 15:13 -0600, Brian King wrote:
> Any reason the other sg patch I submitted didn't get pushed?
Er ... I didn't notice it go by and no-one told me?
> http://marc.theaimsgroup.com/?l=linux-scsi&m=113753907627483&w=2
>
> I was hoping to see this one go into the rc fixes, since without
> it ipr's RAID configuration tools do not work.
In theory, it only affects the sg path, the path via the ULD device node
should already be fixed, so any management tool could use the sd (or st
or sr) node instead ... you probably want to do that anyway to avoid
mapping issues between the sg and sd nodes.
James
next prev parent reply other threads:[~2006-01-31 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 20:56 [GIT PATCH] SCSI bug fixes for 2.6.16-rc1 James Bottomley
2006-01-31 21:13 ` Brian King
2006-01-31 23:09 ` James Bottomley [this message]
2006-01-31 23:18 ` Brian King
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=1138748990.3307.33.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=brking@us.ibm.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