From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Cc: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 00/10] cfg80211: move reg hints to workqueue
Date: Fri, 13 Feb 2009 21:50:49 -0800 [thread overview]
Message-ID: <20090214055049.GC5769@tesla> (raw)
In-Reply-To: <1234589627-16977-1-git-send-email-lrodriguez@atheros.com>
On Fri, Feb 13, 2009 at 09:33:37PM -0800, Luis Rodriguez wrote:
> This series does prep work and then the actual work to move the
> cfg80211 driver and userspace regulatory hints onto a workqueue.
> This also cleans up the core reg hint onto its own routine which
> addresses some of Johannes comments about the branching on the
> assert_cfg80211_mutex(). We also now do a cleanup the comment
> style on reg.c.
I forgot to mention this is now rebased on top of Johannes' two
nl80211 patches:
nl80211: lock rtnl around all operations
genetlink: introduce pre/post methods
Luis
prev parent reply other threads:[~2009-02-14 5:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 5:33 [PATCH 00/10] cfg80211: move reg hints to workqueue Luis R. Rodriguez
2009-02-14 5:33 ` [PATCH 01/10] cfg80211: rename cfg80211_registered_device's idx to wiphy_idx Luis R. Rodriguez
2009-02-14 5:33 ` [PATCH 02/10] cfg80211: add wiphy_idx_valid to check for wiphy_idx sanity Luis R. Rodriguez
2009-02-14 5:33 ` [PATCH 03/10] cfg80211: rename cfg80211_drv_mutex to cfg80211_mutex Luis R. Rodriguez
2009-02-14 5:33 ` [PATCH 04/10] nl80211: disallow user requests prior to regulatory_init() Luis R. Rodriguez
2009-02-15 10:58 ` Johannes Berg
2009-02-16 8:13 ` Luis R. Rodriguez
2009-02-16 8:49 ` Johannes Berg
2009-02-16 9:01 ` Luis R. Rodriguez
2009-02-14 5:33 ` [PATCH 05/10] cfg80211: add regulatory_hint_core() to separate the core reg hint Luis R. Rodriguez
2009-02-15 10:59 ` Johannes Berg
2009-02-16 8:14 ` Luis R. Rodriguez
2009-02-16 8:50 ` Johannes Berg
2009-02-16 9:17 ` Luis R. Rodriguez
2009-02-16 9:22 ` Johannes Berg
2009-02-16 9:29 ` Luis R. Rodriguez
2009-02-14 5:33 ` [PATCH 06/10] cfg80211: propagate -ENOMEM during regulatory_init() Luis R. Rodriguez
2009-02-15 11:01 ` Johannes Berg
2009-02-16 8:18 ` Luis R. Rodriguez
2009-02-16 8:52 ` Johannes Berg
2009-02-16 9:09 ` Luis R. Rodriguez
2009-02-16 9:15 ` Johannes Berg
2009-02-16 9:24 ` Luis R. Rodriguez
2009-02-14 5:33 ` [PATCH 07/10] cfg80211: add assert_cfg80211_lock() to ensure proper protection Luis R. Rodriguez
2009-02-15 11:01 ` Johannes Berg
2009-02-16 8:19 ` Luis R. Rodriguez
2009-02-14 5:33 ` [PATCH 08/10] cfg80211: make regulatory_request use wiphy_idx instead of wiphy Luis R. Rodriguez
2009-02-15 11:04 ` Johannes Berg
2009-02-16 9:55 ` Luis R. Rodriguez
2009-02-16 10:02 ` Johannes Berg
2009-02-16 10:11 ` Luis R. Rodriguez
2009-02-16 10:20 ` Johannes Berg
2009-02-16 11:11 ` Luis R. Rodriguez
2009-02-14 5:33 ` [PATCH 09/10] cfg80211: move regulatory hints to workqueue Luis R. Rodriguez
2009-02-15 11:10 ` Johannes Berg
2009-02-16 9:48 ` Luis R. Rodriguez
2009-02-16 9:55 ` Johannes Berg
2009-02-16 10:09 ` Luis R. Rodriguez
2009-02-16 10:18 ` Johannes Berg
2009-02-14 5:33 ` [PATCH 10/10] cfg80211: comments style cleanup Luis R. Rodriguez
2009-02-14 5:50 ` Luis R. Rodriguez [this message]
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=20090214055049.GC5769@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).