From: James Bottomley <James.Bottomley@steeleye.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Frank Borich <Frank_Borich@us.xyratex.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] 2.4.23
Date: 28 Dec 2003 14:45:40 -0600 [thread overview]
Message-ID: <1072644341.1784.17.camel@mulgrave> (raw)
In-Reply-To: <20031228201020.C22668@infradead.org>
On Sun, 2003-12-28 at 14:10, Christoph Hellwig wrote:
> I'm not too happy about the form of this patch. Could you cook up one
> for 2.6.0 that adds a function pointer to poke at the inquiry data
> to the blacklist? We could backport it to 2.4 later.
Actually, this can't really be done at all for 2.6 since we're extremely
careful not to get inquiry data beyond byte 56 and this patch is looking
into the vendor specific area at 96.
James
next prev parent reply other threads:[~2003-12-28 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 16:13 [PATCH] 2.4.23 Frank Borich
2003-12-28 20:10 ` Christoph Hellwig
2003-12-28 20:45 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-31 15:14 Frank Borich
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=1072644341.1784.17.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Frank_Borich@us.xyratex.com \
--cc=hch@infradead.org \
--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