From: Ondrej Zary <linux@rainbow-software.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH net-next] drivers/net: delete old 8bit ISA 3c501 driver.
Date: Sat, 19 May 2012 10:58:41 +0200 [thread overview]
Message-ID: <201205191058.45328.linux@rainbow-software.org> (raw)
In-Reply-To: <20120518220305.GC15256@windriver.com>
On Saturday 19 May 2012 00:03:06 Paul Gortmaker wrote:
> [Re: [PATCH net-next] drivers/net: delete old 8bit ISA 3c501 driver.] On
18/05/2012 (Fri 20:16) Ondrej Zary wrote:
> > On Friday 18 May 2012 19:39:29 Paul Gortmaker wrote:
> > > It was amusing that linux was able to make use of this 1980's
> > > technology on machines long past its intended lifespan, but
> > > it probably should go now -- it is causing issues in some
> > > distros[1], and while that might be fixable, it is just not
> > > worth it.
> > >
> > > [1]
> > > http://www.linuxquestions.org/questions/linux-networking-3/3com-3c501-c
> > >ard- not-detecting-934344/
> >
> > That looks like a bug elsewhere and removing this driver will not fix it.
>
> You miss the point. We've got someone with a modern i7 machine who is
> getting confused by seeing messages from some ancient 3c501 driver, but
> he doesn't have the context to know it is ancient and the message is a
> red herring. Will it fix a distro's broken init that tries to modprobe
> everything? No. Will it help by not muddying the waters with
> meaningless printk from 3c501 that confuse users? Yes.
Are you going to remove all drivers that complain that the HW is not present
because some broken script is trying to modprobe them all? Or only the first
one? 3c501 is probably the first in alphabet. You remove that and the script
will modprobe 3c503 then...
--
Ondrej Zary
next prev parent reply other threads:[~2012-05-19 8:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 17:39 [PATCH net-next] drivers/net: delete old 8bit ISA 3c501 driver Paul Gortmaker
2012-05-18 18:16 ` Ondrej Zary
2012-05-18 22:03 ` Paul Gortmaker
2012-05-19 8:58 ` Ondrej Zary [this message]
2012-05-20 16:41 ` Paul Gortmaker
2012-05-21 13:42 ` David Laight
2012-05-21 18:46 ` Alan Cox
2012-05-19 12:30 ` Alan Cox
2012-05-19 22:33 ` David Miller
2012-05-20 16:08 ` Paul Gortmaker
2012-05-19 3:54 ` David Miller
2012-05-19 12:31 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2012-05-20 16:02 Emmanuel Fusté
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=201205191058.45328.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=alan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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).