From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: don't use master netdev name
Date: Tue, 09 Jun 2009 10:47:49 -0400 [thread overview]
Message-ID: <1244558869.895.7.camel@mj> (raw)
In-Reply-To: <1244557112.4672.20.camel@johannes.local>
On Tue, 2009-06-09 at 16:18 +0200, Johannes Berg wrote:
> Always use the wiphy name instead.
No objections against the patch.
Maybe we could use wiphy names for the network devices? That is,
wmaster0 would become phy0 and so on. Using two names for the same
thing is confusing. What's better is that we won't have wmaster0
corresponding to phy1 after the driver is reloaded. We'll have "phy1"
in both namespaces.
I wish we could hide those master devices using some "hidden network
device" attribute, but it's not happening.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-06-09 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 14:18 [PATCH] mac80211: don't use master netdev name Johannes Berg
2009-06-09 14:47 ` Pavel Roskin [this message]
2009-06-09 14:49 ` Johannes Berg
2009-06-09 14:53 ` Pavel Roskin
2009-06-09 15:40 ` Marcel Holtmann
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=1244558869.895.7.camel@mj \
--to=proski@gnu.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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