public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: Pavel Machek <pavel@ucw.cz>, Adrian Bunk <bunk@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove CONFIG_EXPERIMENTAL
Date: Mon, 26 Nov 2007 23:34:11 -0500	[thread overview]
Message-ID: <20071127043411.GF15764@redhat.com> (raw)
In-Reply-To: <20547.1196135084@turing-police.cc.vt.edu>

On Mon, Nov 26, 2007 at 10:44:44PM -0500, Valdis.Kletnieks@vt.edu wrote:
 
 > I suspect that given the "once it escapes, it's cast in stone" view we take
 > towards user-visible API/etc, there isn't much *real* room for an
 > 'EXPERIMENTAL' flag anymore.  Most of the usage should probably be confined to
 > individual drivers, where all we should need is a 'default n' and suitable
 > warning verbiage in the Kconfig file warning about the driver eating your
 > filesystems and small animals for breakfast.

Potential corruptors are usually flagged with (DANGEROUS) in the text,
(One may argue that they shouldn't have escaped -mm)

 >  We certainly shouldn't have
 > one big flag for *all* in-progress drivers - I don't need to accidentally
 > enable a busticated ethernet driver because I want a USB widget.

So no ethernet driver at all is better than a broken but mostly working one?
Again if it isn't mostly working, it shouldn't have escaped -mm

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-11-27  4:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-25 16:16 [2.6 patch] remove CONFIG_EXPERIMENTAL Adrian Bunk
2007-11-26 12:27 ` Pavel Machek
2007-11-26 18:57   ` Adrian Bunk
2007-11-27  3:44   ` Valdis.Kletnieks
2007-11-27  4:34     ` Dave Jones [this message]
2007-11-27  6:13       ` Valdis.Kletnieks
2007-11-28 12:38 ` Krzysztof Halasa
  -- strict thread matches above, loose matches on Subject: below --
2007-12-11 22:21 Adrian Bunk
2008-01-01 13:48 Adrian Bunk
2008-01-01 14:23 ` Alan Cox
2008-01-01 15:17   ` Adrian Bunk
2008-01-01 16:07     ` Alan Cox
2008-01-01 16:33       ` Adrian Bunk
2008-01-01 17:35         ` Alan Cox
2008-01-01 18:14           ` Jon Smirl
2008-01-02  0:06           ` Adrian Bunk
2008-01-01 14:26 ` Ingo Molnar
2008-01-01 14:30   ` Alan Cox
2008-01-01 14:57     ` Adrian Bunk
2008-01-01 15:06     ` Ingo Molnar
2008-01-01 18:04     ` Jan Engelhardt
2008-01-10 22:18 ` Ralf Baechle
2008-01-11 10:41   ` Paul Mundt

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=20071127043411.GF15764@redhat.com \
    --to=davej@redhat.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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