From: Stephen Hemminger <shemminger@osdl.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
jgarzik@pobox.com, mlindner@syskonnect.de,
rroesler@syskonnect.de
Subject: Re: [patch 2.6.14-rc4 0/3] sk98lin: neuter and prepare for removal
Date: Tue, 18 Oct 2005 18:38:24 -0700 [thread overview]
Message-ID: <4355A390.9090309@osdl.org> (raw)
In-Reply-To: <10182005213059.12304@bilbo.tuxdriver.com>
John W. Linville wrote:
>These patches take steps towards removing sk98lin from the upstream
>kernel.
>
> -- Remove sk98lin's MODULE_DEVICE_TABLE to avoid
> confusing userland tools about which driver to load;
>
> -- Mark sk98lin as Obsolete in the MAINTAINERS file; and,
>
> -- Add sk98lin to the feature-removal-schedule.txt file in the
> Documentation directory.
>
>I accept the possibility that I may be jumping the gun on this.
>However, I think it is worth opening this discussion.
>
>Patches to follow...
>
>
I applaud the initiative, but this it is too premature to obsolete the
existing driver. There may be lots of chip versions and other variables
that make
the existing driver a better choice. Maybe eepro100 is a better target
for removal right now.
next prev parent reply other threads:[~2005-10-19 1:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 1:30 [patch 2.6.14-rc4 0/3] sk98lin: neuter and prepare for removal John W. Linville
2005-10-19 1:31 ` [patch 2.6.14-rc4 1/3] sk98lin: remove MODULE_DEVICE_TABLE to avoid conflicts w/ skge John W. Linville
2005-10-19 1:31 ` [patch 2.6.14-rc4 2/3] MAINTAINERS: mark the sk98lin driver as obsolete John W. Linville
2005-10-19 1:31 ` [patch 2.6.14-rc4 3/3] Documentation: add sk98lin to the feature-removal-schedule John W. Linville
2005-10-19 1:38 ` Stephen Hemminger [this message]
2005-10-19 1:41 ` [patch 2.6.14-rc4 0/3] sk98lin: neuter and prepare for removal John W. Linville
2005-10-19 2:28 ` Jeff Garzik
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=4355A390.9090309@osdl.org \
--to=shemminger@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mlindner@syskonnect.de \
--cc=netdev@vger.kernel.org \
--cc=rroesler@syskonnect.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).