From: Johannes Berg <johannes@sipsolutions.net>
To: Denis Kenzior <denkenz@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [RFC v2 0/3] Improve wireless netdev detection
Date: Wed, 03 Aug 2016 08:59:35 +0200 [thread overview]
Message-ID: <1470207575.2638.12.camel@sipsolutions.net> (raw)
In-Reply-To: <1468044967-9236-1-git-send-email-denkenz@gmail.com> (sfid-20160709_002109_981191_724B98E0)
On Sat, 2016-07-09 at 01:16 -0500, Denis Kenzior wrote:
> The current mechanism to detect hot-plug / unplug of wireless devices
> is
> somewhat arcane. One has to listen to NEW_WIPHY/DEL_WIPHY events
> over
> nl80211 as well as RTM_NEWLINK / RTM_DELLINK events over rtnl, then
> somehow find a correlation between these events. This involves
> userspace
> sending GET_INTERFACE or GET_WIPHY commands to the kernel, which
> incurs
> additional roundtrips.
>
> This patch series proposes that NEW_INTERFACE and DEL_INTERFACE
> events are
> always emitted, regardless of whether a netdev was added/removed by
> the
> driver or explicitly via NEW_INTERFACE/DEL_INTERFACE commands.
>
> v2: Squished patches 2+3, 4+5. DEL_INTERFACE event notification is
> now
> sent inside cfg80211_unregister_wdev instead of
> nl80211_del_interface.
>
Looks fine to me, care to resend as [PATCH]?
johannes
prev parent reply other threads:[~2016-08-03 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 6:16 [RFC v2 0/3] Improve wireless netdev detection Denis Kenzior
2016-07-09 6:16 ` [RFC v2 1/3] nl80211: Add nl80211_notify_iface Denis Kenzior
2016-07-09 14:05 ` Marcel Holtmann
2016-07-10 18:42 ` Arend Van Spriel
2016-07-10 19:47 ` Marcel Holtmann
2016-07-10 23:49 ` Julian Calaby
2016-07-11 7:39 ` Marcel Holtmann
2016-07-11 9:34 ` Arend Van Spriel
2016-07-09 6:16 ` [RFC v2 2/3] core: Always notify of new wireless netdevs Denis Kenzior
2016-07-09 6:16 ` [RFC v2 3/3] core: Always notify when wireless netdev is removed Denis Kenzior
2016-08-03 6:59 ` Johannes Berg [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=1470207575.2638.12.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=denkenz@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).