linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: jgarzik@pobox.com, akpm@digeo.com
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Remove net drivers depending on OBSOLETE
Date: Mon, 14 Jul 2003 00:29:45 +0200	[thread overview]
Message-ID: <20030713222945.GC12104@fs.tum.de> (raw)

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?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


             reply	other threads:[~2003-07-13 22:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-13 22:29 Adrian Bunk [this message]
2003-07-14  8:05 ` Remove net drivers depending on OBSOLETE Alan Cox
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=20030713222945.GC12104@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=akpm@digeo.com \
    --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).