From: Greg KH <greg@kroah.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, jbenc@suse.cz
Subject: Re: [RFC] convert wiphy to struct device
Date: Fri, 23 Feb 2007 12:19:54 -0800 [thread overview]
Message-ID: <20070223201954.GA1609@kroah.com> (raw)
In-Reply-To: <1172242788.3870.46.camel@johannes.berg>
On Fri, Feb 23, 2007 at 03:59:48PM +0100, Johannes Berg wrote:
> Ok so I did the wiphy stuff w/o knowing that class devs are apparently
> deprecated. Below is a patch to convert it.
>
> However, that patch has a problem. As discussed on netdev in the thread
> "Converting network devices from class devices causes namespace
> pollution" we'll have the same problem here, currently after the patch
> this means that wiphys and netdevs will share the same namespace within
> the device directory.
>
> I think the generic code Greg promised in that thread will fix it by
> renaming the symlink to "ieee80211:wiphy0" instead of just "wiphy0" but
> I'd like to have confirmation about that.
Yes it will, I'm working on that patch right now...
thanks,
greg k-h
next prev parent reply other threads:[~2007-02-23 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 0:58 [RFC PATCH] d80211: fix build break from netdev class_device -> device changes John W. Linville
2007-02-21 10:45 ` Johannes Berg
2007-02-21 13:32 ` John W. Linville
2007-02-23 14:59 ` [RFC] convert wiphy to struct device Johannes Berg
2007-02-23 20:19 ` Greg KH [this message]
2007-02-23 20:33 ` Johannes Berg
2007-02-21 17:45 ` [RFC PATCH] d80211: fix build break from netdev class_device -> device changes Jiri Benc
2007-02-21 17:49 ` Michael Buesch
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=20070223201954.GA1609@kroah.com \
--to=greg@kroah.com \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.