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 21:30:41 +0100 [thread overview]
Message-ID: <1147379442.26130.85.camel@localhost.localdomain> (raw)
In-Reply-To: <1147367677.26087.47.camel@c-67-180-134-207.hsd1.ca.comcast.net>
On Iau, 2006-05-11 at 10:14 -0700, Daniel Walker wrote:
> So it should try to write something even on an error ? It looks like it
> would be really difficult to drop the data off the BHs without actually
> doing the write .. The most straight forward way to handle the error
> would be write all the data copied ..
copy_from_user zero fills failure space so that bit is an accounting job
only.
next prev parent reply other threads:[~2006-05-11 20:18 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
2006-05-11 17:14 ` Daniel Walker
2006-05-11 20:30 ` Alan Cox [this message]
-- 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=1147379442.26130.85.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;
as well as URLs for NNTP newsgroup(s).