[lkml]   [2007]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.


Would it be possible to get this patch merged
(or at least DEPRECATED part of it)?

I think that the patch is useful and that the distinction between
DEPRECATED and OBSOLETE options is quite clear:

* DEPRECATED == new better code is available, old code scheduled for removal

* OBSOLETE == no replacement yet but the code is broken by design
and unreliable, not scheduled for removal yet (BTW Robert, I think
CONFIG_OBSOLETE should also be "default y", at least initially)

I would like to start using CONFIG_DEPRECATED and CONFIG_OBSOLETE
for some IDE config config options/features (not drivers) in the future.


On Sunday 18 February 2007 18:06, Robert P. J. Day wrote:
> Add two new maturity levels of DEPRECATED and OBSOLETE to the kbuild
> structure.
> Signed-off-by: Robert P. J. Day <>
> ---
> one more time, i'll see if i can get this into the main tree, since
> previous attempts just seem to disappear into the void, even though
> several people seemed to think it was a good idea.
> diff --git a/init/Kconfig b/init/Kconfig
> index a3f83e2..acc0052 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -29,9 +29,10 @@ config EXPERIMENTAL
> <file:Documentation/BUG-HUNTING>, and
> <file:Documentation/oops-tracing.txt> in the kernel source).
> - This option will also make obsoleted drivers available. These are
> - drivers that have been replaced by something else, and/or are
> - scheduled to be removed in a future kernel release.
> + At the moment, this option also makes obsolete drivers available,
> + but such drivers really should be removed from the EXPERIMENTAL
> + category and added to either DEPRECATED or OBSOLETE, depending
> + on their status.
> Unless you intend to help test and develop a feature or driver that
> falls into this category, or you have a situation that requires
> @@ -40,6 +41,29 @@ 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.
> +config DEPRECATED
> + bool "Prompt for deprecated code/drivers"
> + default y
> + ---help---
> + Code that is tagged as "deprecated" is officially still available
> + for use but will typically have already been scheduled for removal
> + at some point, so it's in your best interests to start looking for
> + an alternative.
> +
> + Check the file Documentation/feature-removal-schedule.txt to see
> + if a particular feature has an official scheduled removal date.
> +
> +config OBSOLETE
> + bool "Prompt for obsolete code/drivers"
> + default n
> + ---help---
> + Code that is tagged as "obsolete" is officially no longer supported
> + and shouldn't play a part in any normal build, but those features
> + might still be available if you absolutely need access to them.
> +
> + You are *strongly* discouraged from continuing to depend on
> + obsolete code on an ongoing, long-term basis.
> +
> config BROKEN
> bool
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-02-18 19:33    [W:0.109 / U:1.344 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site