From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "David D. Hagood" <wowbagger@sktc.net>
Cc: Adrian Bunk <bunk@fs.tum.de>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: time for some drivers to be removed?
Date: 27 Jul 2003 21:40:43 +0100 [thread overview]
Message-ID: <1059338443.13875.2.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3F241DC0.7080408@sktc.net>
On Sul, 2003-07-27 at 19:45, David D. Hagood wrote:
> I would disagree - OBSOLETE to me means just that - that module is
> obsolete. Minix FS, OSS (as opposed to ALSA), and the old non-SCSI,
> non-IDE HD interfaces would be OBSOLETE.
>
> Besides, I have seen cases where Firewire modules wouldn't build for
> some period of time - would you deem them OBSOLETE?
The code in question is obsolete if it wont build because its out of date
with respect to the core. The point I was trying to make is we have a
definition (have had since 2.2) and actively use it. So there is nothing
to invent here
next prev parent reply other threads:[~2003-07-28 1:07 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 [this message]
2003-07-27 20:56 ` Adrian Bunk
2003-07-27 20:56 ` Alan Cox
2003-07-28 2:23 ` Herbert Pötzl
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=1059338443.13875.2.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--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).