From: James Bottomley <James.Bottomley@SteelEye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Christoph Hellwig <hch@infradead.org>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: PATCH: (as373) Let LLD specify INQUIRY length
Date: 15 Oct 2004 14:28:07 -0500 [thread overview]
Message-ID: <1097868494.2588.23.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0410151426180.1052-100000@ida.rowland.org>
On Fri, 2004-10-15 at 13:30, Alan Stern wrote:
> Nobody has responded to it. Is there some particular person I should send
> this to? Or should I change the patch, so that it merely addresses the
> issue at hand without simplifying the entire subroutine?
OK, sorry, I have it now ... it was in a reply to a patch that I'd
previously applied, so I thought I already had it.
James
next prev parent reply other threads:[~2004-10-15 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 15:53 PATCH: (as284c) Add BLIST_INQUIRY_36 to all USB blacklist entries Alan Stern
2004-08-26 19:11 ` Christoph Hellwig
2004-08-26 19:27 ` Alan Stern
2004-09-07 20:47 ` PATCH: (as373) Let LLD specify INQUIRY length Alan Stern
2004-10-15 18:30 ` Alan Stern
2004-10-15 19:28 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-28 20:25 Alan Stern
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=1097868494.2588.23.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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