From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Russell King <rmk@arm.linux.org.uk>
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 23:31:35 +1100 [thread overview]
Message-ID: <43F31F27.6070908@yahoo.com.au> (raw)
In-Reply-To: <20060215101837.GE21003@flint.arm.linux.org.uk>
Russell King wrote:
> 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.
>
I just mean, to get an agreement (or at least nobody complaining)
before renumbering it again.
I don't think it should be too much of a problem unless it hits 2.6.16
(2.6.16-rc4 would be undesirable too I guess).
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-02-15 17:55 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
2006-02-15 12:31 ` Nick Piggin [this message]
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=43F31F27.6070908@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-arch@vger.kernel.org \
--cc=mst@mellanox.co.il \
--cc=rdreier@cisco.com \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.