linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jeff Garzik <jeff@garzik.org>
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:06:18 -0400	[thread overview]
Message-ID: <1149771978.3436.4.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <44880BEA.90707@garzik.org>

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?

> 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.

James



  parent reply	other threads:[~2006-06-08 13:06 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 [this message]
2006-06-08 13:26     ` Jeff Garzik
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=1149771978.3436.4.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=hch@lst.de \
    --cc=jeff@garzik.org \
    --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).