From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Hemminger <shemminger@osdl.org>
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 21:41:03 -0400 [thread overview]
Message-ID: <20051019014101.GC6687@tuxdriver.com> (raw)
In-Reply-To: <4355A390.9090309@osdl.org>
On Tue, Oct 18, 2005 at 06:38:24PM -0700, Stephen Hemminger wrote:
> 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;
> 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.
That's cool...but I still think the first one (removing the
MODULE_DEVICE_TABLE) is worthwhile. At least that gets more testers
for skge.
What do you think?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2005-10-19 1:41 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 ` [patch 2.6.14-rc4 0/3] sk98lin: neuter and prepare for removal Stephen Hemminger
2005-10-19 1:41 ` John W. Linville [this message]
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=20051019014101.GC6687@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlindner@syskonnect.de \
--cc=netdev@vger.kernel.org \
--cc=rroesler@syskonnect.de \
--cc=shemminger@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.