From: Adrian Bunk <email@example.com> To: "David D. Hagood" <firstname.lastname@example.org> Cc: "Robert P. J. Day" <email@example.com>, Linux kernel mailing list <firstname.lastname@example.org> Subject: Re: time for some drivers to be removed? Date: Sun, 27 Jul 2003 18:18:12 +0200 [thread overview] Message-ID: <20030727161812.GQ22218@fs.tum.de> (raw) In-Reply-To: <3F23F6EB.email@example.com> On Sun, Jul 27, 2003 at 10:59:39AM -0500, David D. Hagood wrote: >... > An item with a BROKEN flag would NOT be built in an ALLYES or ALLMODULE > configuration - it would require the user to explicitly enable the item > in the configuration, and the user would be notified that the module in > question was not compiling/linking the last time the configuration data > was updated by the kernel team. >... I tend to disagree. IMHO every selectable configuration should result in a kernel that compiles. Yes, it's neaarly impossible to achieve this 100%, but at least on i386 we are in 2.4 near to it for all not-very-obscure configurations. Where's the win if you are able to select an option that doesn't compile? This will only cause confusion for people who compile more into the kernel than needed (but it does no harm). Don't forget: The vast majorit of people compiling the kernel don't know anything about the internals of the kernel. If you _really_ want to see the cmpile errors it's easy to edit the Kconfig file. 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:[~2003-07-27 16:03 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-24 12:20 Robert P. J. Day 2003-07-24 14:58 ` Alan Cox 2003-07-24 15:34 ` Bas Mevissen 2003-07-24 17:32 ` Diego Calleja García 2003-07-24 17:50 ` Robert P. J. Day 2003-07-24 19:16 ` Diego Calleja García 2003-07-24 19:43 ` Robert P. J. Day 2003-07-24 18:02 ` Samuel Flory 2003-07-24 19:07 ` Alan Cox 2003-07-25 10:48 ` Bas Mevissen 2003-07-27 15:31 ` Adrian Bunk 2003-07-27 15:59 ` David D. Hagood 2003-07-27 16:18 ` Adrian Bunk [this message] 2003-07-27 16:40 ` Alan Cox 2003-07-27 17:00 ` Adrian Bunk 2003-07-27 18:45 ` David D. Hagood 2003-07-27 20:40 ` Alan Cox 2003-07-27 20:56 ` Adrian Bunk 2003-07-27 20:56 ` Alan Cox 2003-07-28 2:23 ` Herbert Pötzl 2003-07-29 19:33 ` Adrian Bunk 2003-08-13 20:16 ` Bill Davidsen 2003-08-09 18:04 ` David Woodhouse 2003-08-09 19:36 ` Adrian Bunk 2003-07-24 14:43 John Bradford 2003-07-24 19:24 ` Brian Jackson 2003-07-24 18:29 John Bradford 2003-07-24 18:31 ` Robert P. J. Day 2003-07-24 19:31 ` Eli Carter 2003-07-25 10:48 ` Bas Mevissen 2003-07-25 11:10 John Bradford 2003-07-27 16:22 John Bradford 2003-07-28 7:12 linux 2003-08-05 12:42 Mikael Pettersson 2003-08-05 13:03 ` Adrian Bunk 2003-08-05 13:35 ` Mikael Pettersson 2003-08-05 13:48 ` Adrian Bunk 2003-08-05 14:01 ` Mikael Pettersson 2003-08-06 10:06 ` Claus-Justus Heine 2003-08-09 19:40 ` Adrian Bunk 2003-08-05 16:35 ` Alan Cox 2003-08-05 18:47 ` Leopold Gouverneur 2003-08-13 20:55 John Bradford 2003-08-13 20:50 ` Adrian Bunk 2003-08-13 20:55 ` Bill Davidsen 2003-08-14 5:34 John Bradford
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=20030727161812.GQ22218@fs.tum.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: time for some drivers to be removed?' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).