From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-ide@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: ata_sff_data_xfer* return value
Date: Sun, 8 Nov 2009 20:00:50 +0000 [thread overview]
Message-ID: <20091108200050.20d96a44@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <m37hu0bywp.fsf@intrepid.localdomain>
On Sun, 08 Nov 2009 20:27:02 +0100
Krzysztof Halasa <khc@pm.waw.pl> wrote:
> Hi,
>
> I wonder if this is entirely correct? If so, why?
It is correct. We return the bytes consumed as it may well not be the
same as the total bytes requested. In practice we don't currently do a
great deal with it even with ATAPI but it's useful for doing bug checks.
next prev parent reply other threads:[~2009-11-08 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 19:27 ata_sff_data_xfer* return value Krzysztof Halasa
2009-11-08 20:00 ` Alan Cox [this message]
2009-11-08 20:06 ` Krzysztof Halasa
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=20091108200050.20d96a44@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=khc@pm.waw.pl \
--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