From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: introduce critical protocol indication from user-space
Date: Thu, 11 Apr 2013 12:47:27 +0200 [thread overview]
Message-ID: <516694BF.7090701@broadcom.com> (raw)
In-Reply-To: <1365501997.8465.23.camel@jlt4.sipsolutions.net>
On 04/09/2013 12:06 PM, Johannes Berg wrote:
> On Mon, 2013-04-08 at 11:09 +0200, Arend van Spriel wrote:
>> +void cfg80211_crit_proto_stopped(struct wireless_dev *wdev)
>> +{
>> + struct cfg80211_registered_device *rdev;
>> +
>> + rdev = wiphy_to_dev(wdev->wiphy);
>> + WARN_ON(!rdev->crit_proto_started);
>> + rdev->crit_proto_started = false;
>> +}
>
> Oh, so you don't want to tell userspace?
Just an observation will looking for an example of netlink event
messaging to user-space. I noticed that the cfg80211_ft_event() function
used fixed GFP_KERNEL value. Should event functions always have a gfp_t
parameter?
Gr. AvS
next prev parent reply other threads:[~2013-04-11 10:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 9:09 [PATCH] cfg80211: introduce critical protocol indication from user-space Arend van Spriel
2013-04-09 10:06 ` Johannes Berg
2013-04-09 19:54 ` Arend van Spriel
2013-04-09 20:42 ` Johannes Berg
2013-04-10 11:49 ` Arend van Spriel
2013-04-10 13:21 ` Johannes Berg
2013-04-11 10:47 ` Arend van Spriel [this message]
2013-04-11 12:34 ` Johannes Berg
2013-04-11 10:39 ` [PATCH V6] " Arend van Spriel
2013-04-16 14:12 ` Johannes Berg
2013-04-16 21:19 ` Arend van Spriel
2013-04-16 21:43 ` Johannes Berg
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=516694BF.7090701@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--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).