From: Linus Torvalds <torvalds@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Zach Brown <zach.brown@oracle.com>,
bcrl@kvack.org, linux-aio@kvack.org
Subject: Re: [PATCH] aio_write should tell userspace about partial writes
Date: Wed, 12 Mar 2008 12:59:36 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.00.0803121255400.3557@woody.linux-foundation.org> (raw)
In-Reply-To: <200803120939.59915.rusty@rustcorp.com.au>
On Wed, 12 Mar 2008, Rusty Russell wrote:
>
> [ Linus, please apply. This patch was discussed and acked before,
> but somehow got lost. ]
Rusty, please *look* at your patches.
It's pretty obvious even from just the patch that the patch has already
been applied, and that the only reason you think it hasn't is that you use
some crap-for-brains SCM model where you apply patches with GNU patch and
allow fuzz, so it applied cleanly *again*.
I assume that it's quilt messing up again.
In particular, this already went in as commit
7adfa2ff3efa02a7a9f2632d2d2662d3e5eb5304, and I know for a *fact* that it
is in your tree too, since the patch itself clearly has that code double:
> && iocb->ki_nbytes - iocb->ki_left)
> ret = iocb->ki_nbytes - iocb->ki_left;
Lookie above: those two lines are part of the thing that already got
applied! If it hadn't been applied, it would look like
if ((ret == 0) || (iocb->ki_left == 0))
ret = iocb->ki_nbytes - iocb->ki_left;
instead.
I *hate* people who "merge" using patches, and then to make it even worse
use a non-zero fuzz factor.
Linus
next prev parent reply other threads:[~2008-03-12 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 22:39 Rusty Russell
2008-03-12 19:59 ` Linus Torvalds [this message]
2008-03-12 22:12 ` Rusty Russell
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=alpine.LFD.1.00.0803121255400.3557@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=zach.brown@oracle.com \
/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
all inboxes | Powered by JetHome®