From: "Herbert Pötzl" <herbert@13thfloor.at>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Adrian Bunk <bunk@fs.tum.de>,
"David D. Hagood" <wowbagger@sktc.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: time for some drivers to be removed?
Date: Mon, 28 Jul 2003 04:23:36 +0200 [thread overview]
Message-ID: <20030728022336.GC32505@www.13thfloor.at> (raw)
In-Reply-To: <1059339370.13871.4.camel@dhcp22.swansea.linux.org.uk>
On Sun, Jul 27, 2003 at 09:56:11PM +0100, Alan Cox wrote:
> On Sul, 2003-07-27 at 21:56, Adrian Bunk wrote:
> > That's no problem for me.
> >
> > The only question is how to call the option that allows building only on
> > UP (e.g. cli/sti usage in the driver)? My suggestion was BROKEN_ON_SMP,
> > would you suggest OBSOLETE_ON_SMP?
>
> Interesting question - whatever I guess. We don't have an existing convention.
> How many drivers have we got nowdays that failing on just SMP ?
I'm no native speaker, but Webster says:
obsolete:
a) no longer in use or no longer useful
b) of a kind or style no longer current
broken:
2) damaged or altered by breaking
5) not complete or full
so I would prefer BROKEN over OBSOLETE, at least
for drivers which are known _not_ to work as expected,
but OBSOLETE over BROKEN for oldfashioned, but working
drivers superceeded by newer ones ...
JMHO,
Herbert
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-07-28 2:09 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 12:20 time for some drivers to be removed? Robert P. J. Day
2003-07-24 14:58 ` Alan Cox
2003-07-24 15:34 ` Bas Mevissen
2003-07-24 17:32 ` Diego Calleja García
2003-07-24 17:50 ` Robert P. J. Day
2003-07-24 19:16 ` Diego Calleja García
2003-07-24 19:43 ` Robert P. J. Day
2003-07-24 18:02 ` Samuel Flory
2003-07-24 19:07 ` Alan Cox
2003-07-25 10:48 ` Bas Mevissen
2003-07-27 15:31 ` Adrian Bunk
2003-07-27 15:59 ` David D. Hagood
2003-07-27 16:18 ` Adrian Bunk
2003-07-27 16:40 ` Alan Cox
2003-07-27 17:00 ` Adrian Bunk
2003-07-27 18:45 ` David D. Hagood
2003-07-27 20:40 ` Alan Cox
2003-07-27 20:56 ` Adrian Bunk
2003-07-27 20:56 ` Alan Cox
2003-07-28 2:23 ` Herbert Pötzl [this message]
2003-07-29 19:33 ` Adrian Bunk
2003-08-13 20:16 ` Bill Davidsen
2003-08-09 18:04 ` David Woodhouse
2003-08-09 19:36 ` Adrian Bunk
2003-07-24 14:43 John Bradford
2003-07-24 19:24 ` Brian Jackson
2003-07-24 18:29 John Bradford
2003-07-24 18:31 ` Robert P. J. Day
2003-07-24 19:31 ` Eli Carter
2003-07-25 10:48 ` Bas Mevissen
2003-07-25 11:10 John Bradford
2003-07-27 16:22 John Bradford
2003-07-28 7:12 linux
2003-08-05 12:42 Mikael Pettersson
2003-08-05 13:03 ` Adrian Bunk
2003-08-05 13:35 ` Mikael Pettersson
2003-08-05 13:48 ` Adrian Bunk
2003-08-05 14:01 ` Mikael Pettersson
2003-08-06 10:06 ` Claus-Justus Heine
2003-08-09 19:40 ` Adrian Bunk
2003-08-05 16:35 ` Alan Cox
2003-08-05 18:47 ` Leopold Gouverneur
2003-08-13 20:55 John Bradford
2003-08-13 20:50 ` Adrian Bunk
2003-08-13 20:55 ` Bill Davidsen
2003-08-14 5:34 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=20030728022336.GC32505@www.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wowbagger@sktc.net \
/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).