From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Add netdev name to NL80211_CMD_STOP_AP event?
Date: Wed, 10 Jun 2015 23:49:12 +0200 [thread overview]
Message-ID: <1433972952.3145.19.camel@sipsolutions.net> (raw)
In-Reply-To: <5578AF90.5030609@candelatech.com>
On Wed, 2015-06-10 at 14:43 -0700, Ben Greear wrote:
> I was thinking netdevice might go away before user-space can decode the
> message ( I was assuming that on delete you would stop and very shortly
> after that delete the netdev).
Yeah, but in that case ... does it matter? :)
> It's a small patch to iw and the kernel as far as I can tell...
It's small *now*, but if we add it to all events it'll end up pretty
big...
johannes
next prev parent reply other threads:[~2015-06-10 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 21:20 Add netdev name to NL80211_CMD_STOP_AP event? Ben Greear
2015-06-10 21:39 ` Johannes Berg
2015-06-10 21:43 ` Ben Greear
2015-06-10 21:49 ` Johannes Berg [this message]
2015-06-10 21:52 ` Ben Greear
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=1433972952.3145.19.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.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).