From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: hostap: handling device renames better
Date: Tue, 05 Aug 2008 16:27:19 -0400 [thread overview]
Message-ID: <1217968039.29886.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1217967824.3603.62.camel@johannes.berg>
On Tue, 2008-08-05 at 22:23 +0200, Johannes Berg wrote:
> On Tue, 2008-08-05 at 16:23 -0400, Dan Williams wrote:
>
> > How are drivers made aware that their device's name has changed so they
> > could potentially update things they stick in /proc or wherever? hostap
> > and airo come to mind as current users of /proc.
>
> You can register a netdevice notifier and follow the renames. mac80211
> does this for the debugfs dir.
Ok, will look into this. Thanks!
Dan
prev parent reply other threads:[~2008-08-05 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 20:23 hostap: handling device renames better Dan Williams
2008-08-05 20:23 ` Johannes Berg
2008-08-05 20:27 ` Dan Williams [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=1217968039.29886.6.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--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