linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Add netdev name to  NL80211_CMD_STOP_AP event?
Date: Wed, 10 Jun 2015 14:20:17 -0700	[thread overview]
Message-ID: <5578AA11.2020505@candelatech.com> (raw)

While trying to make 'iw' able to print out something useful for
the 'stop_ap' event, I notice there is not really any human friendly
info in the message (just phy id (which may not match phy name), ifindex, and some other
wiphy related numeric ID.

Any reason not to add the netdev name (NL80211_ATTR_IFNAME) to this and
related messages?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


             reply	other threads:[~2015-06-10 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 21:20 Ben Greear [this message]
2015-06-10 21:39 ` Add netdev name to NL80211_CMD_STOP_AP event? Johannes Berg
2015-06-10 21:43   ` Ben Greear
2015-06-10 21:49     ` Johannes Berg
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=5578AA11.2020505@candelatech.com \
    --to=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).