linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Riley Williams" <Riley@Williams.Name>
To: "Adrian Bunk" <bunk@fs.tum.de>
Cc: "Linux Kernel" <Linux-Kernel@Vger.Kernel.Org>
Subject: Re: [2.6 patch] let broken drivers depend on BROKEN{,ON_SMP}
Date: Wed, 30 Jul 2003 08:44:25 +0100	[thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAOEMMFBAA.Riley@Williams.Name> (raw)
In-Reply-To: <20030729195932.GR28767@fs.tum.de>

Hi Adrian.

 > - I do prefer BROKEN, Alan prefers OBSOLETE
 >   a s/BROKEN/OBSOLETE/g is acceptable for me

To me at least, BROKEN and OBSOLETE have different meanings,
and choice of which to use should depend on the circumstances.
Here's my choice of definitions for the cases that I can see:

 * Driver has been replaced by a newer driver, and the old
   driver is currently retained for cases that don't yet
   work with the replacement. Driver will be removed in a
   future kernel once the replacement handles all reported
   cases.

		CONFIG_OBSOLETE

 * Driver is for hardware that is not supported in modern
   computers, and is retained for use with older computers
   only. Driver will not be removed, but is not expected to
   be compiled by most users.

		CONFIG_ANTIQUE

 * Driver does not work, and is thus disabled. If it is not
   fixed in the near future, it will be considered to be
   OBSOLETE as well.

		CONFIG_BROKEN

 * Driver works on uniprocessor but not on SMP and is thus
   disabled when compiling for SMP. It is assumed that the
   driver will be fixed for SMP if relevant.

		CONFIG_BROKEN_ON_SMP

 * Driver was BROKEN some considerable number of releases
   ago, and has never been fixed. It is thus assumed that
   the driver is for some device that none of the kernel
   developers is using. The driver will be removed in the
   transition to the next major release if it retains this
   status.

		CONFIG_BROKEN && CONFIG_OBSOLETE

Personally, I'd like to see CONFIG_ANTIQUE (defaulting to "n")
as a dependency for all drivers matching the description above
simply to cut down on the amount of irrelevant choices in the
configuration process.

Best wishes from Riley.
---
 * Nothing as pretty as a smile, nothing as ugly as a frown.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.504 / Virus Database: 302 - Release Date: 24-Jul-2003


  reply	other threads:[~2003-07-30  7:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 19:59 [2.6 patch] let broken drivers depend on BROKEN{,ON_SMP} Adrian Bunk
2003-07-30  7:44 ` Riley Williams [this message]
2003-07-30  9:11 John Bradford
2003-07-30 10:44 ` Adrian Bunk
2003-07-30 16:04   ` Tomas Szepe
2003-07-30 16:18     ` Adrian Bunk
2003-07-31  9:15       ` Tomas Szepe
2003-08-02 19:47         ` Adrian Bunk
2003-08-13 14:50         ` Bill Davidsen
2003-08-13 15:31           ` Jeff Garzik
2003-08-13 19:17             ` Adrian Bunk
2003-08-13 21:06             ` Bill Davidsen
2003-08-17  9:39               ` Rob Landley
2003-08-18 23:03                 ` Bill Davidsen
2003-07-30 11:29 John Bradford
2003-07-30 11:37 ` Adrian Bunk
2003-07-30 11:53   ` Jan Evert van Grootheest
2003-07-31  9:41 John Bradford
2003-08-02 19:48 ` Adrian Bunk
2003-08-13 20:40 John Bradford
2003-08-13 21:03 ` Adrian Bunk
2003-08-14  5:28 John Bradford
2003-08-17 21:27 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=BKEGKPICNAKILKJKMHCAOEMMFBAA.Riley@Williams.Name \
    --to=riley@williams.name \
    --cc=Linux-Kernel@Vger.Kernel.Org \
    --cc=bunk@fs.tum.de \
    /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;
as well as URLs for NNTP newsgroup(s).