From: Kay Sievers <kay.sievers@vrfy.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Greg KH <greg@kroah.com>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by default
Date: Wed, 20 Jan 2010 18:53:49 +0100 [thread overview]
Message-ID: <ac3eb2511001200953g3fc2be3ay30174b0429707c93@mail.gmail.com> (raw)
In-Reply-To: <20100117065803.6e5e089e@infradead.org>
On Sun, Jan 17, 2010 at 15:58, Arjan van de Ven <arjan@infradead.org> wrote:
> On Fri, 15 Jan 2010 10:03:41 -0800
> Greg KH <greg@kroah.com> wrote:
>> > removing experimental is fine... but setting it by default is a bit
>> > over the top and very inconsistent with how the 'default' option is
>> > used.
>>
>> Why?
>
> because the convention is that we use "default y" only for those things
> that used to be on, and are now turned into a config option.
Oh, I never heard of such a convention. Sure, we can remove that "y",
if this is the way it should be used, not be used.
Looking at the current Kconfig files many "default y" looks more like:
"stuff that should be in a kernel to work in a common setup". I see
new functionality often switched on with that flag.
As said, I don't mind dropping that "y", if there is such a convention.
Thanks,
Kay
next prev parent reply other threads:[~2010-01-20 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 21:47 Kay Sievers
2010-01-15 14:08 ` Stefan Richter
2010-01-15 18:02 ` Greg KH
2010-01-15 14:56 ` Arjan van de Ven
2010-01-15 18:03 ` Greg KH
2010-01-15 20:57 ` Alan Cox
2010-01-16 15:51 ` Kay Sievers
2010-01-16 16:27 ` Alan Cox
2010-01-16 20:11 ` Arjan van de Ven
2010-01-17 7:56 ` Pavel Machek
2010-01-17 14:58 ` Arjan van de Ven
2010-01-20 17:53 ` Kay Sievers [this message]
2010-01-21 6:05 ` Arjan van de Ven
2010-01-21 16:37 ` Greg KH
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=ac3eb2511001200953g3fc2be3ay30174b0429707c93@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®