From: "Jouni Malinen" <jkm@devicescape.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, Jiri Benc <jbenc@suse.cz>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Larry Finger <larry.finger@lwfinger.net>,
Pavel Roskin <proski@gnu.org>, Alex Davis <alex14641@yahoo.com>,
linux-wireless@vger.kernel.org
Subject: Re: Patch to allow specification of interface name prefix
Date: Wed, 28 Feb 2007 11:21:47 -0800 [thread overview]
Message-ID: <20070228192147.GE31074@devicescape.com> (raw)
In-Reply-To: <20070228183535.GB5353@tuxdriver.com>
On Wed, Feb 28, 2007 at 01:35:35PM -0500, John W. Linville wrote:
> On Wed, Feb 28, 2007 at 08:44:37AM -0800, Jouni Malinen wrote:
> > Why would we need to change anything now? What's wrong with wlan#?
>
> See the earlier parts of the thread... :-)
I've seen a somewhat vague comment about some sort of decision on this
front, but no one seems to be able to point to any level of details on
what was agreed on and if yes, when and by whom. I have seen number of
discussions on the topic of what the interfaces should be named, but
none of those seem to be going anywhere and I have not seen any
consensus on this topic. As such, the best thing to do seems to be not
to do anything, i.e., not rename wlan# to anything else. If someone
claims that d80211 is changing the existing behavior, I would just like
to point out that wlan# is already used in the current mainline kernel
and that argument does not sound reasonable.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2007-02-28 19:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 4:06 Patch to allow specification of interface name prefix Alex Davis
2007-02-25 4:30 ` Pavel Roskin
2007-02-25 4:39 ` Larry Finger
2007-02-26 23:02 ` Stephen Hemminger
2007-02-27 1:33 ` John W. Linville
2007-02-27 10:16 ` Jiri Benc
2007-02-27 17:41 ` Stephen Hemminger
2007-02-27 18:21 ` Ben Greear
2007-02-27 18:52 ` Pavel Roskin
2007-02-27 19:15 ` Johannes Berg
2007-02-27 18:55 ` Luis R. Rodriguez
2007-02-28 1:25 ` John W. Linville
2007-02-28 8:51 ` Johannes Berg
2007-02-28 16:44 ` Jouni Malinen
2007-02-28 16:50 ` Johannes Berg
2007-02-28 16:54 ` Luis R. Rodriguez
2007-02-28 16:55 ` Jouni Malinen
2007-02-28 18:35 ` John W. Linville
2007-02-28 19:21 ` Jouni Malinen [this message]
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=20070228192147.GE31074@devicescape.com \
--to=jkm@devicescape.com \
--cc=alex14641@yahoo.com \
--cc=jbenc@suse.cz \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=proski@gnu.org \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).