From: Johannes Berg <johannes@sipsolutions.net>
To: Arik Nemtsov <arik@wizery.com>
Cc: linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: Re: [PATCH 1/2] regulatory: use correct regulatory initiator on wiphy register
Date: Thu, 25 Jul 2013 09:53:24 +0200 [thread overview]
Message-ID: <1374738804.8827.4.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1374413809-26005-1-git-send-email-arik@wizery.com> (sfid-20130721_154507_440351_5B8F6C3E)
On Sun, 2013-07-21 at 16:36 +0300, Arik Nemtsov wrote:
> The current regdomain was not always set by the core. This causes
> cards with a custom regulatory domain to ignore user initiated changes
> if done before the card was registered.
Applied, thanks.
johannes
prev parent reply other threads:[~2013-07-25 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 13:36 [PATCH 1/2] regulatory: use correct regulatory initiator on wiphy register Arik Nemtsov
2013-07-21 13:36 ` [PATCH 2/2] regulatory: take RTNL when restoring settings on CRDA timeout Arik Nemtsov
2013-07-21 14:10 ` Sujith Manoharan
2013-07-21 14:18 ` Arik Nemtsov
2013-07-23 18:21 ` [PATCH 1/2] regulatory: use correct regulatory initiator on wiphy register Luis R. Rodriguez
2013-07-25 7:53 ` Johannes Berg [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=1374738804.8827.4.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arik@wizery.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.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