public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] don't allow users to set CONFIG_BROKEN=y
Date: Fri, 6 Jan 2006 19:58:12 +0100	[thread overview]
Message-ID: <20060106185812.GZ12131@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0601061038130.11324@shark.he.net>

On Fri, Jan 06, 2006 at 10:39:30AM -0800, Randy.Dunlap wrote:
> On Fri, 6 Jan 2006, Jesper Juhl wrote:
> 
> > On 1/6/06, Adrian Bunk <bunk@stusta.de> wrote:
> > > On Fri, Jan 06, 2006 at 06:49:55PM +0100, Jesper Juhl wrote:
> > > > On 1/6/06, Adrian Bunk <bunk@stusta.de> wrote:
> > > > > Do not allow people to create configurations with CONFIG_BROKEN=y.
> > > > >
> > > > > The sole reason for CONFIG_BROKEN=y would be if you are working on
> > > > > fixing a broken driver, but in this case editing the Kconfig file is
> > > > > trivial.
> > > > >
> > > > > Never ever should a user enable CONFIG_BROKEN.
> > > > >
> > > > I disagree (slightly) with this patch for a few reasons:
> > > >
> > > > - It's very convenient to be able to enable it through menuconfig.
> > >
> > > And when do you really need it?
> > >
> > Hmm, when I'm looking for broken stuff to fix ;)
> > I guess you are right, ordinary users don't need it.. Ok, count me in
> > as supporting this move.
> 
> I'm having a little trouble determining why it matters.
> 
> Are you trying to cut down on lkml bug reports or just make
> it harder on everyone?

I'm trying to remove a small trap for users.

> ~Randy

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-01-06 18:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 17:35 [2.6 patch] don't allow users to set CONFIG_BROKEN=y Adrian Bunk
2006-01-06 17:41 ` Russell King
2006-01-06 17:54   ` Adrian Bunk
2006-01-06 17:49 ` Jesper Juhl
2006-01-06 18:06   ` Adrian Bunk
2006-01-06 18:26     ` Jesper Juhl
2006-01-06 18:39       ` Randy.Dunlap
2006-01-06 18:58         ` Adrian Bunk [this message]
2006-01-06 19:14       ` Jan Engelhardt
2006-01-06 21:11     ` David Lang
2006-01-06 22:37       ` Adrian Bunk
2006-01-06 22:39         ` David Lang
2006-01-06 22:53           ` Adrian Bunk
2006-01-06 22:25   ` Daniel Barkalow
  -- strict thread matches above, loose matches on Subject: below --
2006-01-19  1:40 Adrian Bunk
2005-12-11 18:52 [2.6 patch] defconfig's shouldn't " Adrian Bunk
2005-12-11 19:21 ` Russell King
2005-12-11 19:31   ` Adrian Bunk
2005-12-11 19:44     ` Russell King
2005-12-13  0:10       ` Adrian Bunk
2005-12-13 13:34         ` Simon Richter
2005-12-13 14:00           ` Adrian Bunk
2005-12-13 17:31             ` Russell King
2005-12-13 18:05               ` [2.6 patch] don't allow users to " Adrian Bunk
2005-12-13 18:28                 ` Geert Uytterhoeven
2005-12-13 18:51                   ` Adrian Bunk
2005-12-13 18:59                   ` Jesper Juhl
2005-12-13 20:01                 ` Russell King
2005-12-13 20:19                   ` Adrian Bunk
2005-12-13 22:01                     ` Russell King

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=20060106185812.GZ12131@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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