From: Jeff Garzik <jgarzik@pobox.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: davem@redhat.com, alan@lxorguk.ukuu.org.uk, haveblue@us.ibm.com,
akpm@digeo.com, rmk@arm.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: The magical mystical changing ethernet interface order
Date: Sun, 11 May 2003 14:41:03 -0400 [thread overview]
Message-ID: <3EBE993F.1090604@pobox.com> (raw)
In-Reply-To: <20030508093058.3bf3b6ba.rddunlap@osdl.org>
Randy.Dunlap wrote:
> I don't care what the exact implementation is, but anything except
> depending on link (tools) order is better than now IMO.
Well, The Leader Has Spoken, even though I disagree w/ him on this :)
Short term, addressing $subject, somebody needs to look into fixing up
2.5 net driver link order to match history. History is probably 2.2 in
this case, if there is a disparity between 2.2 and 2.4.
Volunteers?
Jeff
next prev parent reply other threads:[~2003-05-11 18:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 13:14 The magical mystical changing ethernet interface order Russell King
2003-05-07 15:18 ` Dick Streefland
2003-05-07 15:38 ` Jeff Garzik
2003-05-07 15:24 ` Randy.Dunlap
2003-05-07 17:14 ` Russell King
2003-05-07 22:04 ` Andrew Morton
2003-05-07 22:28 ` Dave Hansen
2003-05-08 12:05 ` David S. Miller
2003-05-08 14:55 ` Alan Cox
2003-05-08 14:54 ` David S. Miller
2003-05-08 16:24 ` Arnaldo Carvalho de Melo
2003-05-08 16:26 ` Jeff Garzik
2003-05-08 16:30 ` Randy.Dunlap
2003-05-11 18:41 ` Jeff Garzik [this message]
2003-05-08 17:56 ` Kai Germaschewski
2003-05-08 17:36 ` Linus Torvalds
2003-05-09 6:51 ` Richard Henderson
2003-05-08 19:32 Jean Tourrilhes
2003-05-08 21:43 ` Eli Carter
2003-05-08 22:19 ` Jean Tourrilhes
2003-05-08 21:46 ` Alan Cox
2003-05-08 23:23 ` Randy.Dunlap
2003-05-08 23:38 Ray Lee
2003-05-09 12:41 ` Dick Streefland
2003-05-09 14:33 ` Mr. James W. Laferriere
2003-05-10 7:42 Thomas Hood
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=3EBE993F.1090604@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rmk@arm.linux.org.uk \
/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).