From: "H. Peter Anvin" <hpa@zytor.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ok to kill "ether=" kernel parm?
Date: Tue, 28 Aug 2007 09:45:05 -0700 [thread overview]
Message-ID: <46D45111.2040600@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708280307350.3354@localhost.localdomain>
Robert P. J. Day wrote:
> given that "ether=" has been officially obsolete since 2.6.18
> (replaced by "netdev="), is there any reason to keep it around? or
> can it be blasted?
That sounds like way too short of a timeline for breaking people's
working boot setup. For a lot of people, 2.6.18->current is going to be
a single step.
-hpa
next prev parent reply other threads:[~2007-08-28 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 7:08 ok to kill "ether=" kernel parm? Robert P. J. Day
2007-08-28 16:45 ` H. Peter Anvin [this message]
2007-08-28 17:03 ` Robert P. J. Day
2007-08-28 17:23 ` H. Peter Anvin
2007-08-28 17:58 ` Robert P. J. Day
2007-08-28 18:51 ` Alexey Dobriyan
2007-08-29 14:35 ` Denys Vlasenko
2007-08-29 14:28 ` Robert P. J. Day
2007-08-28 18:12 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2007-08-28 18:43 H. Peter Anvin
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=46D45111.2040600@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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 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.