From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Christoph Hellwig <hch@lst.de>,
jejb@SteelEye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] fix up request buffer reference in various scsi drivers
Date: Thu, 08 Jun 2006 09:26:42 -0400 [thread overview]
Message-ID: <44882592.5090701@garzik.org> (raw)
In-Reply-To: <1149771978.3436.4.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Thu, 2006-06-08 at 07:37 -0400, Jeff Garzik wrote:
>> False statement, for libata.
>
> Could you amplify this statement, please ... I looked through the head
> of libata-dev and it seems that these are still the only two bufflen
> uses, which still do look obviously wrong ... I don't see where the
> problem in libata with this is?
Christoph's false statement is: "Using the buffer and bufflen fields
means they do very broken things in error handling."
libata does not do "very broken things in error handling."
>> Please CC the author (me) or linux-ide, at least, when you touch
>> libata.
>
> The tradition is that for infrastructure changes like this, particularly
> ones that are trivial, as this appears to be, you simply copy the scsi
> list and don't have to sweep up the individual maintainers of each
> driver.
This is apparently an EH-related patch, and libata uses SCSI EH very
differently from all other drivers. In this case, Christoph's "very
broken" justification is clearly inaccurate, and thus a CC is obviously
warranted.
Also, I remind people constantly of this, so I'm sure you and Christoph
have heard the request before.
Jeff, the one who forwards to linux-scsi when others forget
next prev parent reply other threads:[~2006-06-08 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-03 11:21 [PATCH] fix up request buffer reference in various scsi drivers Christoph Hellwig
2006-06-08 11:37 ` Jeff Garzik
2006-06-08 13:01 ` Matthew Wilcox
2006-06-08 13:06 ` James Bottomley
2006-06-08 13:26 ` Jeff Garzik [this message]
2006-06-08 13:54 ` James Bottomley
2006-06-08 14:17 ` Jeff Garzik
2006-06-08 14:35 ` James Bottomley
2006-06-08 14:44 ` Jeff Garzik
2006-06-08 17:40 ` James Bottomley
2006-06-08 17:46 ` Christoph Hellwig
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=44882592.5090701@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@SteelEye.com \
--cc=hch@lst.de \
--cc=jejb@SteelEye.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;
as well as URLs for NNTP newsgroup(s).