From: Marc Zyngier <mzyngier@freesurf.fr>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
jgarzik@pobox.com, aeb@cwi.nl
Subject: Re: NICs trading places ?
Date: 29 Mar 2003 10:20:39 +0100 [thread overview]
Message-ID: <wrpisu21qc8.fsf@hina.wild-wind.fr.eu.org> (raw)
In-Reply-To: <20030328224843.GA11980@win.tue.nl>
>>>>> "Andries" == Andries Brouwer <aebr@win.tue.nl> writes:
Andries> I am not quite sure, apologies in case I misremember, but
Andries> maybe the most recent breakage was caused by Marc Zyngier
Andries> with EISA bus changes.
Well, it is not exactly related to EISA bus, although part of the same
patch.
The real problem is that some old drivers are still initialized from
Space.c (they simply do not know about init_etherdev (NULL, ...),
after all these years). So yes, I broke 3c509 in this respect. I also
broke znet if that matters. Oh, and the EISA part of depca in the AC
tree.
So the questions are :
- Should Space.c die ? I think so.
- Should 2.5 be the place and time to kill it ? I also think so.
I know it is a pain for most of us to have interfaces being
renumbered. But relying on something as static as Space.c is the wrong
answer IMHO.
M.
--
Places change, faces change. Life is so very strange.
next prev parent reply other threads:[~2003-03-29 9:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 22:10 Dave Jones
2003-03-28 22:14 ` Jeff Garzik
2003-03-28 22:15 ` jjs
2003-03-28 22:25 ` Joel Becker
2003-03-28 22:27 ` Randy.Dunlap
2003-03-28 22:34 ` Dave Jones
2003-03-28 22:48 ` Andries Brouwer
2003-03-28 23:02 ` Andrew Morton
2003-03-28 23:20 ` Andries Brouwer
2003-03-28 23:41 ` Greg KH
2003-03-28 23:56 ` Jeff Garzik
2003-03-29 0:03 ` Greg KH
2003-03-29 9:20 ` Marc Zyngier [this message]
2003-03-28 23:30 ` Dax Kelson
2003-03-28 23:42 ` Sean Neakums
[not found] <20030328221037.GB25846@suse.de.suse.lists.linux.kernel>
2003-03-29 4:47 ` Andi Kleen
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=wrpisu21qc8.fsf@hina.wild-wind.fr.eu.org \
--to=mzyngier@freesurf.fr \
--cc=aeb@cwi.nl \
--cc=aebr@win.tue.nl \
--cc=davej@codemonkey.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®