From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH 2/4] libata: update ATAPI overflow draining
Date: Fri, 01 Feb 2008 15:34:09 -0500 [thread overview]
Message-ID: <47A38241.9070602@garzik.org> (raw)
In-Reply-To: <11992723711166-git-send-email-htejun@gmail.com>
Tejun,
If you could explain your objection to James's patches in this area, I
would really appreciate it.
We have several conflicting patches in this area, and we need to get the
details sorted.
I think you mentioned a key objection that was we actually need to know
/two/ sizes at the block layer: (1) the size including all padding and
drain buffers, and (2) the raw or "true" size.
Jeff
parent reply other threads:[~2008-02-01 20:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <11992723711166-git-send-email-htejun@gmail.com>]
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=47A38241.9070602@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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