LKML Archive on
help / color / mirror / Atom feed
From: "Robert P. J. Day" <>
To: Linux kernel mailing list <>
Subject: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
Date: Sun, 18 Feb 2007 12:06:56 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0702181203360.5131@CPE00045a9c397f-CM001225dbafb6> (raw)

  Add two new maturity levels of DEPRECATED and OBSOLETE to the kbuild

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.

+	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

Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

             reply	other threads:[~2007-02-18 17:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 17:06 Robert P. J. Day [this message]
2007-02-18 18:35 ` Bartlomiej Zolnierkiewicz
2007-02-18 18:53   ` Robert P. J. Day
2007-02-20 16:27   ` Tilman Schmidt
2007-02-20 18:42     ` Bartlomiej Zolnierkiewicz
2007-02-20 22:52       ` Robert P. J. Day
2007-02-20 23:12         ` Tilman Schmidt
2007-02-20 23:23           ` Robert P. J. Day
2007-02-25 10:42           ` Pavel Machek
2007-02-25 22:59             ` Tilman Schmidt
2007-02-20 22:47     ` Robert P. J. Day
2007-02-20 22:56       ` Sam Ravnborg
2007-02-20 23:01         ` Robert P. J. Day

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0702181203360.5131@CPE00045a9c397f-CM001225dbafb6 \ \ \
    --subject='Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.' \

* 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).