ata_sff_data_xfer* return value

[Krzysztof Halasa]

Hi,

I wonder if this is entirely correct? If so, why?
Only relevant parts left.

* RETURNS:
* Bytes consumed.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
*/
unsigned int ata_sff_data_xfer(struct ata_device *dev, unsigned char *buf,
unsigned int buflen, int rw)
{
unsigned int words = buflen >> 1;

...

/* Transfer trailing byte, if any. */
if (unlikely(buflen & 0x01)) {
...
words++;
}

return words << 1;

same here:

unsigned int ata_sff_data_xfer32(struct ata_device *dev, unsigned char *buf,
unsigned int buflen, int rw)
{
...
return (buflen + 1) & ~1;

Please keep me in CC:, I'm not on the IDE list. Thanks.
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

[Alan Cox]

On Sun, 08 Nov 2009 20:27:02 +0100
Krzysztof Halasa <k...@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.

[Krzysztof Halasa]

Alan Cox <al...@lxorguk.ukuu.org.uk> writes:

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

I see. Thanks.
--
Krzysztof Halasa