public inbox for linux-kernel@vger.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: Fri, 15 Jan 2010 10:03:41 -0800	[thread overview]
Message-ID: <20100115180341.GA12146@kroah.com> (raw)
In-Reply-To: <20100115065638.005ac690@infradead.org>

On Fri, Jan 15, 2010 at 06:56:38AM -0800, Arjan van de Ven wrote:
> On Thu, 14 Jan 2010 22:47:57 +0100
> Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > From: Kay Sievers <kay.sievers@vrfy.org>
> > Subject: Driver-Core: devtmpfs - remove EXPERIMENTAL and enable it by
> > default
> > 
> > All major distros enable devtmpfs on recent systems, so remove
> > the EXPERIMENTAL flag, and enable it by default to reflect how it
> > is used today.
> 
> 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?  All major distros need this at boot time, and as we have been
through a release cycle with the config option, anyone who is
incrementally updating will continue with their existing value.  But new
people coming in, will get the option as it is most likely required to
boot properly.

Makes sense to me.

thanks,

greg k-h

  reply	other threads:[~2010-01-15 18:05 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 [this message]
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

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=20100115180341.GA12146@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox