From: Arnd Bergmann <arnd@arndb.de>
To: Amerigo Wang <xiyou.wangcong@gmail.com>
Cc: Stefani Seibold <stefani@seibold.net>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH 0/7] new kfifo API
Date: Thu, 13 Aug 2009 09:27:21 +0000 [thread overview]
Message-ID: <200908130927.22124.arnd@arndb.de> (raw)
In-Reply-To: <20090813030903.GC5031@cr0.nay.redhat.com>
On Thursday 13 August 2009 03:09:03 Amerigo Wang wrote:
> And, personally I don't like your splitting of these patches,
> I prefer to see kfifo API changes first, then their usages.
Note that they are relatively hard to split without breaking
git-bisect. That can only work if you are able to introduce
the API under a different name first and then change the
users, finally removing the old API.
Arnd <><
prev parent reply other threads:[~2009-08-13 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 22:31 [PATCH 0/7] new kfifo API Stefani Seibold
2009-08-12 14:58 ` Arnd Bergmann
2009-08-12 15:28 ` Stefani Seibold
2009-08-12 16:43 ` Arnd Bergmann
2009-08-13 3:09 ` Amerigo Wang
2009-08-13 9:27 ` Arnd Bergmann [this message]
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=200908130927.22124.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefani@seibold.net \
--cc=xiyou.wangcong@gmail.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