From: Johannes Berg <johannes@sipsolutions.net>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/3] Add mcast event when hwsim radios are created and removed
Date: Mon, 27 Oct 2014 12:31:25 +0100 [thread overview]
Message-ID: <1414409485.3836.5.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1414409397.2705.198.camel@jrissane-mobl.ger.corp.intel.com>
On Mon, 2014-10-27 at 13:29 +0200, Jukka Rissanen wrote:
> Yes, but from generic nl80211 event you cannot know if event is from
> hwsim radio or not. With this patch, the listener can know that the
> radio new/del event is specifically related to hwsim radio.
That's not particularly hard to figure out, for example by looking at
sysfs.
Is this really so time-constrained/important/... that you can't do that?
johannes
next prev parent reply other threads:[~2014-10-27 11:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 10:44 [PATCH 0/3] Add mcast event when hwsim radios are created and removed Jukka Rissanen
2014-10-27 10:44 ` [PATCH 1/3] mac80211-hwsim: Rename CREATE and DESTROY radio to NEW and DEL radio Jukka Rissanen
2014-10-29 15:48 ` Johannes Berg
2014-10-27 10:44 ` [PATCH 2/3] mac80211-hwsim: Provide multicast event for HWSIM_CMD_NEW_RADIO Jukka Rissanen
2014-10-29 15:48 ` Johannes Berg
2014-10-29 15:50 ` Johannes Berg
2014-10-29 15:53 ` Johannes Berg
2014-10-30 14:28 ` Jukka Rissanen
2014-10-27 10:44 ` [PATCH 3/3] mac80211-hwsim: Provide multicast event for HWSIM_CMD_DEL_RADIO Jukka Rissanen
2014-10-27 11:20 ` [PATCH 0/3] Add mcast event when hwsim radios are created and removed Johannes Berg
2014-10-27 11:29 ` Jukka Rissanen
2014-10-27 11:31 ` Johannes Berg [this message]
2014-10-27 11:55 ` Jukka Rissanen
2014-10-27 12:08 ` Johannes Berg
2014-10-27 14:19 ` Marcel Holtmann
2014-10-27 17:34 ` Luca Coelho
2014-10-27 23:14 ` Marcel Holtmann
2014-10-27 23:22 ` Ben Greear
2014-10-28 6:42 ` Luca Coelho
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=1414409485.3836.5.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jukka.rissanen@linux.intel.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).