linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Denis Kenzior <denkenz@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Improve wireless netdev detection
Date: Thu, 11 Aug 2016 14:44:17 +0200	[thread overview]
Message-ID: <1470919457.12075.5.camel@sipsolutions.net> (raw)
In-Reply-To: <1470261515-2830-1-git-send-email-denkenz@gmail.com> (sfid-20160803_161400_172995_F10633C5)

On Wed, 2016-08-03 at 16:58 -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.
> 

Applied. I squashed 1/2 since it's kinda pointless to have a patch
introducing infrastructure that's not used.

I also made some minor cleanups - please check (both that it's right,
and for next time)

johannes

  parent reply	other threads:[~2016-08-11 12:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03 21:58 [PATCH v3 0/3] Improve wireless netdev detection Denis Kenzior
2016-08-03 21:58 ` [PATCH v3 1/3] nl80211: Add nl80211_notify_iface Denis Kenzior
2016-08-03 21:58 ` [PATCH v3 2/3] core: Always notify of new wireless netdevs Denis Kenzior
2016-08-03 21:58 ` [PATCH v3 3/3] core: Always notify when wireless netdev is removed Denis Kenzior
2016-08-11 12:44 ` Johannes Berg [this message]
2016-08-11 16:31   ` [PATCH v3 0/3] Improve wireless netdev detection Denis Kenzior

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=1470919457.12075.5.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).