All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by default
Date: Thu, 21 Jan 2010 08:37:42 -0800	[thread overview]
Message-ID: <20100121163742.GA13222@kroah.com> (raw)
In-Reply-To: <20100120220553.66af4fd7@infradead.org>

On Wed, Jan 20, 2010 at 10:05:53PM -0800, Arjan van de Ven wrote:
> On Wed, 20 Jan 2010 18:53:49 +0100
> Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > 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.
> 
> For example in (this is just the first one google found, there's been a
> bunch of discussion at various times)
> 
> http://article.gmane.org/gmane.linux.kernel/706458
> 
> Linus was rather explicit:
> 
> The rule of thumb should be:
> 
> 	NO NEW FEATURES SHOULD _EVER_ DEFAULT TO 'ON'!

But this is not a "new" feature, it's been around for 6+ months by the
time it hits a release.  Does this imply that we can never change
anything to 'on' in the Kconfig files?

thanks,

greg k-h

      reply	other threads:[~2010-01-21 16:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 21:47 Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by default 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
2010-01-21  6:05         ` Arjan van de Ven
2010-01-21 16:37           ` Greg KH [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=20100121163742.GA13222@kroah.com \
    --to=greg@kroah.com \
    --cc=arjan@infradead.org \
    --cc=kay.sievers@vrfy.org \
    --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 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.