linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, linux@eikelenboom.it,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH v2 0/3] cfg80211: respin reprocessing pending requests
Date: Tue, 25 Feb 2014 17:09:39 -0800	[thread overview]
Message-ID: <1393376982-28276-1-git-send-email-mcgrof@do-not-panic.com> (raw)

Here's a respin. There are no code changes, I just adjusted the
commit logs as that's all the feedback I got from them, and on
the last patch I just don't think a timer is best. If a timer
is desired let me know how much time you want to set it for,
I just don't see how that's any better.

The commit log on the other ones should help let people make
decisions if the implications of not merging this, I'll let
folks make the call about whether or not some of these belong
to stable, I personally don't think so -- but some others may
disagree.

Luis R. Rodriguez (3):
  cfg80211: allow reprocessing of pending requests
  cfg80211: fix processing world regdomain when non modular
  cfg80211: processing regulatory requests on netdev notifier

 net/wireless/reg.c | 16 +++++++++-------
 net/wireless/reg.h |  1 +
 2 files changed, 10 insertions(+), 7 deletions(-)

-- 
1.8.5.3


             reply	other threads:[~2014-02-26  1:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26  1:09 Luis R. Rodriguez [this message]
2014-02-26  1:09 ` [PATCH 1/3] cfg80211: allow reprocessing of pending requests Luis R. Rodriguez
2014-03-03 13:10   ` Johannes Berg
2014-02-26  1:09 ` [PATCH 2/3] cfg80211: fix processing world regdomain when non modular Luis R. Rodriguez
2014-03-03 13:10   ` Johannes Berg
2014-03-14 20:30     ` Colleen T
2014-03-14 20:48       ` Luis R. Rodriguez
2014-03-14 22:12         ` Colleen T
2014-03-15  1:03           ` Luis R. Rodriguez
2014-03-15 15:59             ` Janusz Dziedzic
2014-03-16  4:42               ` Luis R. Rodriguez
2014-03-16 19:04                 ` Colleen T
2014-04-09 16:33                   ` Arik Nemtsov
2014-04-09 19:16                     ` Johannes Berg
2014-04-10  6:13                       ` Arik Nemtsov
2014-04-10  8:01                         ` Johannes Berg
2014-04-10  8:17                           ` Arik Nemtsov
2014-04-10  8:23                             ` Johannes Berg
2014-04-09 20:28                     ` Sander Eikelenboom
2014-04-13 12:50                     ` Eliad Peller
2014-04-14 19:27                       ` Colleen T
2014-04-16 10:38                         ` Arik Nemtsov
2014-04-16 11:01                           ` Janusz Dziedzic
2014-04-16 11:07                             ` Arik Nemtsov
2014-03-19 14:01       ` Johannes Berg
2014-02-26  1:09 ` [PATCH 3/3] cfg80211: processing regulatory requests on netdev notifier Luis R. Rodriguez
2014-02-27 13:21   ` Arik Nemtsov
2014-02-27 17:20     ` Luis R. Rodriguez
2014-02-27 20:31       ` Arik Nemtsov
2014-02-26  7:41 ` [PATCH v2 0/3] cfg80211: respin reprocessing pending requests Sander Eikelenboom

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=1393376982-28276-1-git-send-email-mcgrof@do-not-panic.com \
    --to=mcgrof@do-not-panic.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    /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).