public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: <linville@tuxdriver.com>
Cc: <wireless-regdb@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wireless-regdb: add regulatory rule for US on 60gHz band
Date: Sun, 23 Dec 2012 11:36:03 +0200	[thread overview]
Message-ID: <42386442.bUoSgr792i@lx-vladimir> (raw)
In-Reply-To: <8774585.BvFN3Opv12@lx-vladimir>

On Sunday, December 09, 2012 04:16:21 PM Vladimir Kondratiev wrote:
> Subject: [PATCH] wireless-regdb: add regulatory rule for US on 60gHz band
> 
> There is coming 802.11ad standard that defines WiFi operations on the new band 60g.
> 
> In the US, reference document is:
> 
> http://cfr.regstoday.com/47cfr15.aspx#47_CFR_15p255
> 
> Signed-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
> 

Hi John,

Any comments? Can you please merge this patch?

Same about 2 more, with 60g for Europe and China. Titled as:

[PATCH] wireless-regdb: add regulatory rule for ETSI members on
 60gHz band
[PATCH] wireless-regdb: add regulatory rule for China on 60GHz band

Thanks, Vladimir.

      parent reply	other threads:[~2012-12-23  9:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09 14:16 [PATCH] wireless-regdb: add regulatory rule for US on 60gHz band Vladimir Kondratiev
2012-12-10  9:45 ` [PATCH] wireless-regdb: add regulatory rule for ETSI members " Vladimir Kondratiev
2012-12-10 10:21   ` Johannes Berg
2012-12-10 11:09     ` Vladimir Kondratiev
2012-12-10 11:31       ` Johannes Berg
2012-12-10 12:15         ` Vladimir Kondratiev
2012-12-10 12:33           ` Johannes Berg
2012-12-10 15:48             ` [PATCH v2] " Vladimir Kondratiev
2013-02-06 18:39               ` John W. Linville
2013-02-07  9:27                 ` Vladimir Kondratiev
2012-12-23  9:36 ` Vladimir Kondratiev [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=42386442.bUoSgr792i@lx-vladimir \
    --to=qca_vkondrat@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=wireless-regdb@lists.infradead.org \
    /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