From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Daniel Walker <dwalker@mvista.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] updated idetape gcc 4.1 warning fix
Date: Thu, 11 May 2006 14:11:41 +0100 [thread overview]
Message-ID: <1147353102.26130.6.camel@localhost.localdomain> (raw)
In-Reply-To: <200605101810.k4AIAA8x006488@dwalker1.mvista.com>
On Mer, 2006-05-10 at 11:10 -0700, Daniel Walker wrote:
> I added returns for failures .. I would hope that this doesn't break anything in
> userspace , but I'll confess that I have no way to determin that for certain .
>
> Hows that Alan?
You still need to walk the BHs I think. Also if an error occurs and some
data is successfully transferred the standards explicitly require you
return the amount of data successfully transferred if you report an
error.
next prev parent reply other threads:[~2006-05-11 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 18:10 [PATCH -mm] updated idetape gcc 4.1 warning fix Daniel Walker
2006-05-11 13:11 ` Alan Cox [this message]
2006-05-11 17:14 ` Daniel Walker
2006-05-11 20:30 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2006-05-16 20:23 Daniel Walker
2006-05-10 17:59 Daniel Walker
2006-05-12 11:48 ` Jesper Juhl
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=1147353102.26130.6.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=dwalker@mvista.com \
--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