From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>, Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: [2.6 patch] move STANDALONE to drivers/base/Kconfig
Date: Sat, 17 Jul 2004 22:46:13 +0200 [thread overview]
Message-ID: <20040717204612.GF14733@fs.tum.de> (raw)
In-Reply-To: <20040622053349.GA2738@mars.ravnborg.org>
> > This option is in drivers/base/Kconfig, but the similar option
> > STANDALONE [1] is in init/Kconfig.
> >
> > Shouldn't buoth be at the same place?
> > What about moving STANDALONE ad let it depend on PREVENT_FIRMWARE_BUILD?
>
> STANDALONE avoids any drivers not using external firmware.
> PREVENT_FIRMWARE_BUILD just prevents the supplied firmware to be build.
> So no I do not see they should be dependent.
>
> But for sure they should be located in the same place.
> This is drivers only information and not related to the actual
> maturity of the code - so moving STANDALONE to drivers/base
> makes sense to me.
> Adrian - care to submit a patch?
Sorry for the late answer, the patch is below.
> Sam
cu
Adrian
Move STANDALONE from init/Kconfig to drivers/base/Kconfig .
This way, it's besides PREVENT_FIRMWARE_BUILD.
Signed-off-by: Adrian Bunk <bunk@fs.tum.de>
--- linux-2.6.8-rc1-mm1-full/init/Kconfig.old 2004-07-17 20:07:03.000000000 +0200
+++ linux-2.6.8-rc1-mm1-full/init/Kconfig 2004-07-17 20:07:39.000000000 +0200
@@ -41,15 +41,6 @@
If unsure, say Y
-config STANDALONE
- bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL
- default y
- help
- Select this option if you don't have magic firmware for drivers that
- need it.
-
- If unsure, say Y.
-
config BROKEN
bool
depends on !CLEAN_COMPILE
--- linux-2.6.8-rc1-mm1-full/drivers/base/Kconfig.old 2004-07-17 20:06:36.000000000 +0200
+++ linux-2.6.8-rc1-mm1-full/drivers/base/Kconfig 2004-07-17 20:07:34.000000000 +0200
@@ -1,5 +1,14 @@
menu "Generic Driver Options"
+config STANDALONE
+ bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL
+ default y
+ help
+ Select this option if you don't have magic firmware for drivers that
+ need it.
+
+ If unsure, say Y.
+
config PREVENT_FIRMWARE_BUILD
bool "Prevent firmware from being built"
default y
next prev parent reply other threads:[~2004-07-17 20:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 0:46 2.6.7-mm1 Andrew Morton
2004-06-21 1:40 ` 2.6.7-mm1: empty help text for FB_RIVA_I2C Adrian Bunk
2004-06-21 7:38 ` Antonino A. Daplas
2004-06-21 1:43 ` [patch] 2.6.7-mm1: R8169_NAPI help text Adrian Bunk
2004-06-21 1:55 ` [patch] 2.6.7-mm1: drivers/scsi/hosts.h -> scsi/scsi_host.h Adrian Bunk
2004-06-22 3:48 ` Jeff Garzik
2004-06-21 2:04 ` 2.6.7-mm1 Adrian Bunk
2004-06-22 5:33 ` 2.6.7-mm1 Sam Ravnborg
2004-07-17 20:46 ` Adrian Bunk [this message]
2004-06-21 2:06 ` 2.6.7-mm1 linker trouble with CONFIG_FB_RIVA_I2C=y and modular I2C Matthias Andree
2004-06-21 15:29 ` [patch] " Adrian Bunk
2004-06-22 15:11 ` Matthias Andree
2004-06-21 10:48 ` 2.6.7-mm1 Dominik Karall
2004-06-21 11:00 ` 2.6.7-mm1 Andrew Morton
2004-06-21 11:43 ` 2.6.7-mm1 Dominik Karall
2004-06-23 7:28 ` 2.6.7-mm1 Daniele Venzano
2004-06-21 11:48 ` 2.6.7-mm1 Eric BEGOT
2004-06-21 14:25 ` 2.6.7-mm1 James Morris
2004-06-21 14:38 ` 2.6.7-mm1 Eric BEGOT
2004-06-22 0:15 ` 2.6.7-mm1 Adrian Bunk
2004-06-21 14:32 ` 2.6.7-mm1 (compile stats) John Cherry
2004-06-21 23:05 ` 2.6.7-mm1 I/O regression ? FabF
2004-06-21 23:18 ` FabF
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=20040717204612.GF14733@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox