From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v6 00/15] cfg80211: add a workqueue for regulatory processing
Date: Mon, 23 Feb 2009 18:28:12 -0800 [thread overview]
Message-ID: <20090224022812.GJ4264@tesla> (raw)
In-Reply-To: <1235440617.4455.47.camel@johannes.local>
On Mon, Feb 23, 2009 at 05:56:57PM -0800, Johannes Berg wrote:
> On Sat, 2009-02-21 at 00:04 -0500, Luis R. Rodriguez wrote:
> > I found one bug in my v5 series on the workqueue patch -- I was
> > accessing wiphy->custom_regulatory without first checking if the
> > wiphy existed, in case there are any conflicts I am rebasing the
> > other patches and just sending a new version 6 series.
>
> Did anything else significantly change? I gave it a quick look and it
> seems fine.
Nope, just one line where I forgot to check for wiphy first before checking
for wiphy->custom_regulatory.
Luis
prev parent reply other threads:[~2009-02-24 2:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 5:04 [PATCH v6 00/15] cfg80211: add a workqueue for regulatory processing Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 01/15] cfg80211: rename cfg80211_registered_device's idx to wiphy_idx Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 02/15] cfg80211: add wiphy_idx_valid to check for wiphy_idx sanity Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 03/15] cfg80211: rename cfg80211_drv_mutex to cfg80211_mutex Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 04/15] nl80211: disallow user requests prior to regulatory_init() Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 05/15] cfg80211: add regulatory_hint_core() to separate the core reg hint Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 06/15] cfg80211: propagate -ENOMEM during regulatory_init() Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 07/15] cfg80211: add assert_cfg80211_lock() to ensure proper protection Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 08/15] cfg80211: make regulatory_request use wiphy_idx instead of wiphy Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 09/15] cfg80211: protect first access of last_request on 11d hint under mutex Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 10/15] cfg80211: remove likely from an 11d hint case Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 11/15] cfg80211: free rd on unlikely event on 11d hint Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 12/15] cfg80211: move all regulatory hints to workqueue Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 13/15] cfg80211: comments style cleanup Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 14/15] cfg80211: allow drivers that agree on regulatory to agree Luis R. Rodriguez
2009-02-21 5:04 ` [PATCH v6 15/15] cfg80211: rename regdom_changed to regdom_changes() and use it Luis R. Rodriguez
2009-02-24 1:56 ` [PATCH v6 00/15] cfg80211: add a workqueue for regulatory processing Johannes Berg
2009-02-24 2:28 ` 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=20090224022812.GJ4264@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).