Linux wireless drivers development
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Haim Dreyfuss <haim.dreyfuss@intel.com>
Cc: wireless-regdb@lists.infradead.org,
	linux-wireless@vger.kernel.org, johannes.berg@intel.com
Subject: Re: [PATCH v2 1/2] wireless-regdb: Add wmm rule for EEA and EFTA countries
Date: Tue, 8 May 2018 14:49:15 -0500	[thread overview]
Message-ID: <20180508194915.GA3375@ubuntu-xps13> (raw)
In-Reply-To: <1525363103-8620-1-git-send-email-haim.dreyfuss@intel.com>

On Thu, May 03, 2018 at 06:58:22PM +0300, Haim Dreyfuss wrote:
> The ETSI EN 301 893 v211 (2017-05) standard defines a new channel
> access mechanism that all devices (WLAN and LAA) need to comply with.
> In previous versions the device was allowed by ETSI to implement
> 802.11 channel access mechanism based on a set of priority classes
> which are taken from 802.11.
> According to the new standard there might be some exception
> which require the EEA and the EFTA countries, which adhere
> ETSI rules, to follow more restrictive rules.
> In order to comply with the new standard introduced by ETSI, add
> wmmrule global item with the new ETSI channel mechanism rules.
> Also add wmmrule flag to EEA and EFTA countries.
> 
> Signed-off-by: Haim Dreyfuss <haim.dreyfuss@intel.com>

That's looking better. I did some light testing and nothing blew up with
4.15 or 4.17.

Applied both patches, thanks!

      parent reply	other threads:[~2018-05-08 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 15:58 [PATCH v2 1/2] wireless-regdb: Add wmm rule for EEA and EFTA countries Haim Dreyfuss
2018-05-03 15:58 ` [PATCH v2 2/2] wireless-regdb: Parse wmm rule data Haim Dreyfuss
2018-05-08 19:49 ` Seth Forshee [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=20180508194915.GA3375@ubuntu-xps13 \
    --to=seth.forshee@canonical.com \
    --cc=haim.dreyfuss@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --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