Re: [2.6 patch] remove CONFIG_EXPERIMENTAL

[Jan Engelhardt]

On Jan 1 2008 14:30, Alan Cox wrote:
>> * Adrian Bunk <bunk@xxxxxxxxxx> wrote:
>> 
>> > This patch removes the EXPERIMENTAL option and all dependencies on 
>> > EXPERIMENTAL since they are pointless.
>> 
>> agreed. CONFIG_BROKEN has real use - but CONFIG_EXPERIMENTAL is pretty 
>> pointless in the 90-days kernel development model.
>
>Then I need a replacement equivalent for the ATA layer and all the other
>drivers using it to indicate stuff that *IS* experimental, or not yet
>known to be highly robust. [...]
>
>CONFIG_ATA_EXPERIMENTAL, CONFIG_NET_EXPERIMENTAL,
>CONFIG_VIDEO_EXPERIMENTAL, ... all being added by developers

Yes please.


menuconfig actually supports placing config options in more than one
place, would this be helpful? (besides the itch that it is defined in 
two places.)

---
 drivers/ata/Kconfig |    5 +++++
 init/Kconfig        |    8 ++++++++
 2 files changed, 13 insertions(+)

Index: linux-2.6_nosov/drivers/ata/Kconfig
===================================================================
--- linux-2.6_nosov.orig/drivers/ata/Kconfig
+++ linux-2.6_nosov/drivers/ata/Kconfig
@@ -23,6 +23,11 @@ menuconfig ATA
 
 if ATA
 
+# also see init/Kconfig
+config ATA_EXPERIMENTAL
+	bool "Prompt for experimental libata drivers"
+	depends on EXPERIMENTAL
+
 config ATA_NONSTANDARD
        bool
        default n
Index: linux-2.6_nosov/init/Kconfig
===================================================================
--- linux-2.6_nosov.orig/init/Kconfig
+++ linux-2.6_nosov/init/Kconfig
@@ -40,6 +40,14 @@ config EXPERIMENTAL
 	  you say Y here, you will be offered the choice of using features or
 	  drivers that are currently considered to be in the alpha-test phase.
 
+if EXPERIMENTAL
+
+# also see drivers/ata/Kconfig
+config ATA_EXPERIMENTAL
+	bool "Prompt for experimental libata drivers"
+
+endif # EXPERIMENTAL
+
 config BROKEN
 	bool
 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/