From: Russell King <rmk@arm.linux.org.uk>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: "Michael S. Tsirkin" <mst@mellanox.co.il>,
linux-arch@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Roland Dreier <rdreier@cisco.com>,
Hugh Dickins <hugh@veritas.com>
Subject: Re: [Fwd: Re: [PATCH] madvise MADV_DONTFORK/MADV_DOFORK]
Date: Wed, 15 Feb 2006 10:18:38 +0000 [thread overview]
Message-ID: <20060215101837.GE21003@flint.arm.linux.org.uk> (raw)
In-Reply-To: <43F2E38C.5030602@yahoo.com.au>
On Wed, Feb 15, 2006 at 07:17:16PM +1100, Nick Piggin wrote:
> All I'm saying is that we can easily wait a few days until arch
> maintainers have had a chance to comment (you didn't think you
> were missing anything last time, either).
>
> We can afford to be a little bit careful about changing user APIs.
The new numbers only appeared very recently for ARM (iow, came in
with this mornings git update), so changing them sooner rather than
later would be preferred - cuts down the number of potential kernel
patches/tarballs which have the "wrong" numbers.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-02-15 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 6:18 [Fwd: Re: [PATCH] madvise MADV_DONTFORK/MADV_DOFORK] Nick Piggin
2006-02-15 8:10 ` Michael S. Tsirkin
2006-02-15 8:17 ` Nick Piggin
2006-02-15 8:49 ` Nick Piggin
2006-02-15 12:12 ` Michael S. Tsirkin
2006-02-15 10:18 ` Russell King [this message]
2006-02-15 12:31 ` Nick Piggin
2006-02-15 10:20 ` Michael S. Tsirkin
2006-02-15 12:43 ` Matthew Wilcox
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=20060215101837.GE21003@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-arch@vger.kernel.org \
--cc=mst@mellanox.co.il \
--cc=nickpiggin@yahoo.com.au \
--cc=rdreier@cisco.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