From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wireless-regdb updated, please check!
Date: Sat, 12 Jan 2013 00:40:38 +0100 [thread overview]
Message-ID: <1357947638.9767.8.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130111193922.GD2170@tuxdriver.com> (sfid-20130111_204517_481009_5182122F)
On Fri, 2013-01-11 at 14:39 -0500, John W. Linville wrote:
> All,
>
> I've been sitting on some wireless-regdb patches for some time.
> Mostly this is because I wasn't sure what to do with some/most of them.
> I even still have a few more like that...
Could you also apply "regdb: allow 40 MHz on world roaming channels
12/13" -- we've already applied the same change to the kernel's version
of the world roaming regdomain.
johannes
next prev parent reply other threads:[~2013-01-11 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 19:39 wireless-regdb updated, please check! John W. Linville
2013-01-11 23:40 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-11 20:54 Xose Vazquez Perez
2013-01-11 21:26 ` John W. Linville
2013-01-13 13:25 ` Xose Vazquez Perez
2013-01-13 13:39 ` Xose Vazquez Perez
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=1357947638.9767.8.camel@jlt4.sipsolutions.net \
--to=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).