From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Michael Leun <lkml20140418@newton.leun.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
Arik Nemtsov <arik@wizery.com>,
Sander Eikelenboom <linux@eikelenboom.it>
Subject: Re: [PATCH 0/2] cfg80211: two reg fixes
Date: Tue, 22 Apr 2014 10:04:19 -0700 [thread overview]
Message-ID: <CAB=NE6W64b5VS5pTnxrcRRkRdje6h_hQcGmF9jUiXO55b+nHRw@mail.gmail.com> (raw)
In-Reply-To: <20140422184824.74973bb3@xenia.leun.net>
On Tue, Apr 22, 2014 at 9:48 AM, Michael Leun
<lkml20140418@newton.leun.net> wrote:
> 1611 if (wiphy->regulatory_flags & REGULATORY_COUNTRY_IE_IGNORE)
> 1612 return REG_REQ_IGNORE;
Interesting -- same line as your regression test had found, wiphy->
must be NULL. Digging deeper, you can discard that patch now, we can
rule out the reprocessing of the request.
Luis
next prev parent reply other threads:[~2014-04-22 17:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 3:39 [PATCH 0/2] cfg80211: two reg fixes Luis R. Rodriguez
2014-04-22 3:39 ` [PATCH 1/2] cfg80211: avoid freeing last_request while in flight Luis R. Rodriguez
2014-04-22 15:17 ` Johannes Berg
2014-04-22 3:39 ` [PATCH 2/2] cfg80211: fix processing world regdomain when non modular Luis R. Rodriguez
2014-04-22 15:18 ` Johannes Berg
2014-04-22 15:37 ` Sander Eikelenboom
2014-04-22 16:44 ` Luis R. Rodriguez
2014-09-02 12:00 ` Helmut Schaa
2014-09-05 21:43 ` Luis R. Rodriguez
2014-09-08 9:59 ` Helmut Schaa
2014-09-08 22:27 ` Luis R. Rodriguez
2014-04-22 16:00 ` [PATCH 0/2] cfg80211: two reg fixes Michael Leun
2014-04-22 16:32 ` Luis R. Rodriguez
2014-04-22 16:48 ` Michael Leun
2014-04-22 17:04 ` Luis R. Rodriguez [this message]
2014-04-22 17:30 ` Michael Leun
2014-04-22 17:38 ` Luis R. Rodriguez
2014-04-22 19:48 ` Michael Leun
2014-04-22 20:45 ` Luis R. Rodriguez
2014-04-22 21:32 ` Michael Leun
2014-04-22 21:50 ` Luis R. Rodriguez
2014-04-22 22:53 ` Michael Leun
2014-04-22 23:19 ` Luis R. Rodriguez
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='CAB=NE6W64b5VS5pTnxrcRRkRdje6h_hQcGmF9jUiXO55b+nHRw@mail.gmail.com' \
--to=mcgrof@do-not-panic.com \
--cc=arik@wizery.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=lkml20140418@newton.leun.net \
/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.