From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: linux@eikelenboom.it, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] cfg80211: allow reprocessing of pending requests
Date: Tue, 07 Jan 2014 16:34:09 +0100 [thread overview]
Message-ID: <1389108849.4645.12.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1387486399-4053-2-git-send-email-mcgrof@do-not-panic.com> (sfid-20131219_215331_944250_A52D0D00)
On Thu, 2013-12-19 at 12:53 -0800, Luis R. Rodriguez wrote:
> This addresses the RCU component of allowing us to reprocess
> the last regulatory request.
That commit message makes very little sense to me.
johannes
next prev parent reply other threads:[~2014-01-07 15:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 20:53 [PATCH 0/3] cfg80211: process pending regulatory requests Luis R. Rodriguez
2013-12-19 20:53 ` [PATCH 1/3] cfg80211: allow reprocessing of pending requests Luis R. Rodriguez
2014-01-07 15:34 ` Johannes Berg [this message]
2014-01-23 13:16 ` Sander Eikelenboom
2014-01-24 23:14 ` Luis R. Rodriguez
2014-01-27 10:48 ` Sander Eikelenboom
2014-02-19 0:51 ` Luis R. Rodriguez
2013-12-19 20:53 ` [PATCH 2/3] cfg80211: fix processing world regdomain when non modular Luis R. Rodriguez
2014-01-07 15:35 ` Johannes Berg
2014-02-19 1:10 ` Luis R. Rodriguez
2013-12-19 20:53 ` [PATCH 3/3] cfg80211: processing regulatory requests on netdev notifier Luis R. Rodriguez
2014-01-07 15:35 ` Johannes Berg
2014-02-19 1:24 ` Luis R. Rodriguez
2014-02-19 18:08 ` Luis R. Rodriguez
2013-12-20 12:19 ` [PATCH 0/3] cfg80211: process pending regulatory requests Sander Eikelenboom
2014-01-06 13:10 ` Sander Eikelenboom
2014-01-06 13:32 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2014-02-26 1:09 [PATCH v2 0/3] cfg80211: respin reprocessing pending requests Luis R. Rodriguez
2014-02-26 1:09 ` [PATCH 1/3] cfg80211: allow reprocessing of " Luis R. Rodriguez
2014-03-03 13:10 ` 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=1389108849.4645.12.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=mcgrof@do-not-panic.com \
/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).