From: Andrew Morton <akpm@linux-foundation.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: ebiederm@xmission.com, kir@swsoft.com, containers@lists.osdl.org,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
kir@openvz.org
Subject: Re: [Devel] [PATCH] pidns: Place under CONFIG_EXPERIMENTAL (take 2)
Date: Fri, 26 Oct 2007 19:18:45 -0700 [thread overview]
Message-ID: <20071026191845.fd0f75c8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071027020408.GO30533@stusta.de>
> On Sat, 27 Oct 2007 04:04:08 +0200 Adrian Bunk <bunk@kernel.org> wrote:
> > be happy to hear if someone has a better idea.
>
> There is a difference between "complete the feature" and "early adopters
> to start playing with the feature" on the one side, and making something
> available in a released kernel on the other side.
>
> For development and playing with it it can depend on BROKEN (perhaps
> with the dependency removed through the first -rc kernels), but as soon
> as it's available in a -final kernel the ABI is fixed.
>
Yes, if we're not 100% certain that the interfaces are correnct and unchanging
and that the implementation is solid, we should disable the feature at Kconfig time.
The best option would be to fix things asap. But assuming that option isn't
reasonable and/or safe, we can slip a `depends on BROKEN' into -rc6 then
resume development for 2.6.25.
next prev parent reply other threads:[~2007-10-27 2:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CBC546DD07068244AEC110EFEDA58B7235893F@excite.int.sw-soft.com>
2007-10-26 21:59 ` [Devel] [PATCH] pidns: Place under CONFIG_EXPERIMENTAL (take 2) Eric W. Biederman
2007-10-27 0:24 ` Adrian Bunk
2007-10-27 1:31 ` Eric W. Biederman
2007-10-27 2:04 ` Adrian Bunk
2007-10-27 2:18 ` Andrew Morton [this message]
2007-10-27 3:46 ` Eric W. Biederman
2007-10-27 4:03 ` Adrian Bunk
2007-10-27 4:40 ` Eric W. Biederman
2007-10-27 5:17 ` Adrian Bunk
2007-10-27 4:40 ` Andrew Morton
2007-10-27 7:41 ` Eric W. Biederman
2007-10-29 18:05 ` Cedric Le Goater
2007-10-29 19:11 ` Eric W. Biederman
2007-10-28 16:12 ` Jeremy Fitzhardinge
2007-10-28 17:00 ` Adrian Bunk
2007-10-28 18:31 ` Eric W. Biederman
2007-10-29 10:13 ` Cedric Le Goater
2007-10-29 18:08 ` Eric W. Biederman
2007-10-26 22:34 ` Eric W. Biederman
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=20071026191845.fd0f75c8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=kir@openvz.org \
--cc=kir@swsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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