From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: jgarzik@pobox.com, akpm@digeo.com, linux-net@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Remove net drivers depending on OBSOLETE
Date: 14 Jul 2003 09:05:01 +0100 [thread overview]
Message-ID: <1058169900.554.22.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030713222945.GC12104@fs.tum.de>
On Sul, 2003-07-13 at 23:29, Adrian Bunk wrote:
> The following three net drivers depend in both 2.4 and 2.5 on
> CONFIG_OBSOLETE:
> - FMV18X
> - SEEQ8005
> - SK_G16
>
> Since CONFIG_OBSOLETE is never set they are not selectable.
> Is there any reason why they should stay in the kernel or would you
> accept a patch that removes these drivers?
Seeq hardware turns up now and again, sk_g16 is a pretty rare bit of
hardware but I thought people had it working in current 2.4, fmv18x
I've no idea about. I'll take a look at them
next prev parent reply other threads:[~2003-07-14 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 22:29 Remove net drivers depending on OBSOLETE Adrian Bunk
2003-07-14 8:05 ` Alan Cox [this message]
2003-07-15 16:33 ` Alan Cox
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=1058169900.554.22.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@digeo.com \
--cc=bunk@fs.tum.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/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).