From: Adrian Bunk <bunk@stusta.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Richter <Simon.Richter@hogyros.de>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
tony.luck@intel.com, linux-ia64@vger.kernel.org, matthew@wil.cx,
grundler@parisc-linux.org, parisc-linux@parisc-linux.org,
Paul Mackerras <paulus@samba.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
lethal@linux-sh.org, kkojima@rr.iij4u.or.jp, dwmw2@infradead.org,
linux-mtd@lists.infradead.org
Subject: Re: [2.6 patch] don't allow users to set CONFIG_BROKEN=y
Date: Tue, 13 Dec 2005 18:51:50 +0000 [thread overview]
Message-ID: <20051213185150.GP23349@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0512131926530.17990@pademelon.sonytel.be>
On Tue, Dec 13, 2005 at 07:28:41PM +0100, Geert Uytterhoeven wrote:
> On Tue, 13 Dec 2005, Adrian Bunk 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.
> ^^^^
> OK, a user, not an expert. Let's assume users don't enable EXPERIMENTAL.
Let's assume users don't have any hardware (e.g. several SATA drivers)
that requires EXPERIMENTAL...
> But I'd like to at least have the possibility to enable broken drivers, even if
> it's just for compile regression tests.
If a kernel developer really wants to enable BROKEN drivers, my patch
still gives them the possibility to do so with a trivial edit of
init/Kconfig.
> Gr{oetje,eeting}s,
>
> Geert
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
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@stusta.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: tony.luck@intel.com, linux-ia64@vger.kernel.org,
grundler@parisc-linux.org, matthew@wil.cx,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
lethal@linux-sh.org, Paul Mackerras <paulus@samba.org>,
linux-mtd@lists.infradead.org,
Simon Richter <Simon.Richter@hogyros.de>,
dwmw2@infradead.org, kkojima@rr.iij4u.or.jp,
parisc-linux@parisc-linux.org
Subject: Re: [2.6 patch] don't allow users to set CONFIG_BROKEN=y
Date: Tue, 13 Dec 2005 19:51:50 +0100 [thread overview]
Message-ID: <20051213185150.GP23349@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0512131926530.17990@pademelon.sonytel.be>
On Tue, Dec 13, 2005 at 07:28:41PM +0100, Geert Uytterhoeven wrote:
> On Tue, 13 Dec 2005, Adrian Bunk 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.
> ^^^^
> OK, a user, not an expert. Let's assume users don't enable EXPERIMENTAL.
Let's assume users don't have any hardware (e.g. several SATA drivers)
that requires EXPERIMENTAL...
> But I'd like to at least have the possibility to enable broken drivers, even if
> it's just for compile regression tests.
If a kernel developer really wants to enable BROKEN drivers, my patch
still gives them the possibility to do so with a trivial edit of
init/Kconfig.
> Gr{oetje,eeting}s,
>
> Geert
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
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@stusta.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: tony.luck@intel.com, linux-ia64@vger.kernel.org,
grundler@parisc-linux.org, matthew@wil.cx,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
lethal@linux-sh.org, linux-mtd@lists.infradead.org,
dwmw2@infradead.org, kkojima@rr.iij4u.or.jp,
parisc-linux@parisc-linux.org
Subject: Re: [2.6 patch] don't allow users to set CONFIG_BROKEN=y
Date: Tue, 13 Dec 2005 19:51:50 +0100 [thread overview]
Message-ID: <20051213185150.GP23349@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0512131926530.17990@pademelon.sonytel.be>
On Tue, Dec 13, 2005 at 07:28:41PM +0100, Geert Uytterhoeven wrote:
> On Tue, 13 Dec 2005, Adrian Bunk 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.
> ^^^^
> OK, a user, not an expert. Let's assume users don't enable EXPERIMENTAL.
Let's assume users don't have any hardware (e.g. several SATA drivers)
that requires EXPERIMENTAL...
> But I'd like to at least have the possibility to enable broken drivers, even if
> it's just for compile regression tests.
If a kernel developer really wants to enable BROKEN drivers, my patch
still gives them the possibility to do so with a trivial edit of
init/Kconfig.
> Gr{oetje,eeting}s,
>
> Geert
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
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@stusta.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Richter <Simon.Richter@hogyros.de>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
tony.luck@intel.com, linux-ia64@vger.kernel.org, matthew@wil.cx,
grundler@parisc-linux.org, parisc-linux@parisc-linux.org,
Paul Mackerras <paulus@samba.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
lethal@linux-sh.org, kkojima@rr.iij4u.or.jp, dwmw2@infradead.org,
linux-mtd@lists.infradead.org
Subject: Re: [2.6 patch] don't allow users to set CONFIG_BROKEN=y
Date: Tue, 13 Dec 2005 19:51:50 +0100 [thread overview]
Message-ID: <20051213185150.GP23349@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0512131926530.17990@pademelon.sonytel.be>
On Tue, Dec 13, 2005 at 07:28:41PM +0100, Geert Uytterhoeven wrote:
> On Tue, 13 Dec 2005, Adrian Bunk 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.
> ^^^^
> OK, a user, not an expert. Let's assume users don't enable EXPERIMENTAL.
Let's assume users don't have any hardware (e.g. several SATA drivers)
that requires EXPERIMENTAL...
> But I'd like to at least have the possibility to enable broken drivers, even if
> it's just for compile regression tests.
If a kernel developer really wants to enable BROKEN drivers, my patch
still gives them the possibility to do so with a trivial edit of
init/Kconfig.
> Gr{oetje,eeting}s,
>
> Geert
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
next prev parent reply other threads:[~2005-12-13 18:51 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 18:52 [2.6 patch] defconfig's shouldn't set CONFIG_BROKEN=y Adrian Bunk
2005-12-11 18:52 ` Adrian Bunk
2005-12-11 18:52 ` Adrian Bunk
2005-12-11 19:21 ` Russell King
2005-12-11 19:21 ` Russell King
2005-12-11 19:31 ` Adrian Bunk
2005-12-11 19:31 ` Adrian Bunk
2005-12-11 19:44 ` Russell King
2005-12-11 19:44 ` Russell King
2005-12-13 0:10 ` Adrian Bunk
2005-12-13 0:10 ` Adrian Bunk
2005-12-13 0:10 ` Adrian Bunk
2005-12-13 13:34 ` Simon Richter
2005-12-13 13:34 ` Simon Richter
2005-12-13 13:34 ` Simon Richter
2005-12-13 14:00 ` Adrian Bunk
2005-12-13 14:00 ` Adrian Bunk
2005-12-13 14:00 ` Adrian Bunk
2005-12-13 14:00 ` Adrian Bunk
2005-12-13 17:31 ` Russell King
2005-12-13 17:31 ` Russell King
2005-12-13 17:31 ` Russell King
2005-12-13 17:38 ` Geert Uytterhoeven
2005-12-13 19:53 ` Russell King
2005-12-13 20:09 ` Adrian Bunk
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 [this message]
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
2005-12-12 9:38 ` [2.6 patch] defconfig's shouldn't " David Woodhouse
2005-12-12 9:38 ` David Woodhouse
2005-12-12 9:38 ` David Woodhouse
2005-12-13 0:05 ` [RFC: 2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers Adrian Bunk
2005-12-13 0:06 ` Adrian Bunk
2005-12-14 11:50 ` [2.6 patch] defconfig's shouldn't set CONFIG_BROKEN=y Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2006-01-06 17:35 [2.6 patch] don't allow users to " 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
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
2006-01-19 1:40 Adrian Bunk
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=20051213185150.GP23349@stusta.de \
--to=bunk@stusta.de \
--cc=Simon.Richter@hogyros.de \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=grundler@parisc-linux.org \
--cc=kkojima@rr.iij4u.or.jp \
--cc=lethal@linux-sh.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matthew@wil.cx \
--cc=parisc-linux@parisc-linux.org \
--cc=paulus@samba.org \
--cc=tony.luck@intel.com \
/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.