All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 00/15] cfg80211: add a workqueue for regulatory processing
Date: Wed, 18 Feb 2009 14:20:30 -0800	[thread overview]
Message-ID: <20090218222030.GF4246@tesla> (raw)
In-Reply-To: <20090218221824.GB3953@tuxdriver.com>

On Wed, Feb 18, 2009 at 02:18:24PM -0800, John W. Linville wrote:
> On Tue, Feb 17, 2009 at 08:21:47PM -0800, Luis R. Rodriguez wrote:
> > This series has a few cleanups and minor fixes but mainly
> > adds a workqueue for cfg80211 to use to process all regulatory
> > hints. This v3 changes _all_ regulatory hints to use this
> > workqueue.
> >
> > I've combined this series with my later one that had only 3 patches=
=2E
> >
> > This series is also rebased on today's pull of wl.
> >
> > Luis R. Rodriguez (15):
> >   cfg80211: rename cfg80211_registered_device's idx to wiphy_idx
> >   cfg80211: add wiphy_idx_valid to check for wiphy_idx sanity
> >   cfg80211: rename cfg80211_drv_mutex to cfg80211_mutex
> >   nl80211: disallow user requests prior to regulatory_init()
> >   cfg80211: add regulatory_hint_core() to separate the core reg hin=
t
> >   cfg80211: propagate -ENOMEM during regulatory_init()
> >   cfg80211: add assert_cfg80211_lock() to ensure proper protection
> >   cfg80211: make regulatory_request use wiphy_idx instead of wiphy
> >   cfg80211: protect first access of last_request on 11d hint under
> >     mutex
> >   cfg80211: remove likely from an 11d hint case
> >   cfg80211: free rd on unlikely event on 11d hint
> >   cfg80211: move all regulatory hints to workqueue
> >   cfg80211: comments style cleanup
> >   cfg80211: allow drivers that agree on regulatory to agree
> >   cfg80211: rename regdom_changed to regdom_changes() and use it
>=20
> Not sure what happened, but all I got was this:
>=20
>  271   T Feb 17 Luis R. Rodrigu (  44) [PATCH v3 00/15] cfg80211: add=
 a workqueue for regulatory processing
>  272 O T Feb 17 Luis R. Rodrigu (   0) =E2=94=9C=E2=94=80>[PATCH v3 0=
4/15] nl80211: disallow user requests prior to regulatory_init()
>  273 O T Feb 17 Luis R. Rodrigu (   0) =E2=94=9C=E2=94=80>[PATCH v3 0=
5/15] cfg80211: add regulatory_hint_core() to separate the core reg hin=
t
>  274 O T Feb 17 Luis R. Rodrigu (   0) =E2=94=9C=E2=94=80>[PATCH v3 0=
6/15] cfg80211: propagate -ENOMEM during regulatory_init()
>  275 O T Feb 17 Luis R. Rodrigu (   0) =E2=94=9C=E2=94=80>[PATCH v3 1=
0/15] cfg80211: remove likely from an 11d hint case
>  276 O T Feb 17 Luis R. Rodrigu (   0) =E2=94=94=E2=94=80>[PATCH v3 1=
4/15] cfg80211: allow drivers that agree on regulatory to agree
>=20
> Would you mind resending (at least to my address)?

Sorry about that... Microsoft Exchange 2007 happened. Will resend from =
a less buggy
SMTP somewhere.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-02-18 22:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18  4:21 [PATCH v3 00/15] cfg80211: add a workqueue for regulatory processing Luis R. Rodriguez
2009-02-18  4:21 ` [PATCH v3 04/15] nl80211: disallow user requests prior to regulatory_init() Luis R. Rodriguez
2009-02-18  4:21 ` [PATCH v3 05/15] cfg80211: add regulatory_hint_core() to separate the core reg hint Luis R. Rodriguez
2009-02-18  4:21 ` [PATCH v3 06/15] cfg80211: propagate -ENOMEM during regulatory_init() Luis R. Rodriguez
2009-02-18  4:21 ` [PATCH v3 10/15] cfg80211: remove likely from an 11d hint case Luis R. Rodriguez
2009-02-18  4:22 ` [PATCH v3 14/15] cfg80211: allow drivers that agree on regulatory to agree Luis R. Rodriguez
     [not found] ` <20090218221824.GB3953@tuxdriver.com>
2009-02-18 22:20   ` 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=20090218222030.GF4246@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.