All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>, 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 20:14:51 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0601062013130.28630@yvahk01.tjqt.qr> (raw)
In-Reply-To: <9a8748490601061026t3e467dfdxc90b6403bbd45802@mail.gmail.com>

>> 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 go with it.

I had CONFIG_BROKEN on, which 'cost' me one post to LKML to find out that
CONFIG_MTD_AMD... does rightfully not compile. It (CONFIG_BROKEN/CLEAN_COMPILE)
just confuses.


Jan Engelhardt
-- 

  parent reply	other threads:[~2006-01-06 19:14 UTC|newest]

Thread overview: 39+ 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
2006-01-06 19:14       ` Jan Engelhardt [this message]
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:05                 ` Adrian Bunk
2005-12-13 18:05                 ` Adrian Bunk
2005-12-13 18:28                 ` Geert Uytterhoeven
2005-12-13 18:28                   ` Geert Uytterhoeven
2005-12-13 18:28                   ` Geert Uytterhoeven
2005-12-13 18:28                   ` Geert Uytterhoeven
2005-12-13 18:51                   ` Adrian Bunk
2005-12-13 18:51                     ` Adrian Bunk
2005-12-13 18:51                     ` Adrian Bunk
2005-12-13 18:51                     ` Adrian Bunk
2005-12-13 18:59                   ` Jesper Juhl
2005-12-13 18:59                     ` Jesper Juhl
2005-12-13 18:59                     ` Jesper Juhl
2005-12-13 18:59                     ` Jesper Juhl
2005-12-13 20:01                 ` Russell King
2005-12-13 20:01                   ` Russell King
2005-12-13 20:01                   ` Russell King
2005-12-13 20:19                   ` Adrian Bunk
2005-12-13 20:19                     ` Adrian Bunk
2005-12-13 20:19                     ` Adrian Bunk
2005-12-13 22:01                     ` Russell King
2005-12-13 22:01                       ` Russell King
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=Pine.LNX.4.61.0601062013130.28630@yvahk01.tjqt.qr \
    --to=jengelh@linux01.gwdg.de \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=jesper.juhl@gmail.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 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.