Linux wireless drivers development
 help / color / mirror / Atom feed
From: Gianfranco Costamagna <locutusofborg@debian.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
	"brcm80211-dev-list@broadcom.com"
	<brcm80211-dev-list@broadcom.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "nsmaldone@tierratelematics.com" <nsmaldone@tierratelematics.com>,
	"Marco.Arlone@roj.com" <Marco.Arlone@roj.com>
Subject: Re: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value
Date: Mon, 14 Nov 2016 11:34:13 +0000 (UTC)	[thread overview]
Message-ID: <233918815.6357602.1479123253455@mail.yahoo.com> (raw)
In-Reply-To: <0812c8f2-f0ce-c62c-5f09-fa46dafd630f@broadcom.com>

Hi Arend,


>Finally response. As it turns out the range was explcitly changed

>enabling channels 12 and 13 to be used where applicable. They forgot to
>update the comment.


so, the struct in net/wireless/reg.c is actually used in that case?

static const struct ieee80211_regdomain world_regdom = {

do you plan to update the comment?

thanks!

Gianfranco

  reply	other threads:[~2016-11-14 11:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACJOhtL-oFTJC5j0_+fdecWExZBKvDy13o+UBzw47tyrvD_SJQ@mail.gmail.com>
     [not found] ` <CACJOhtKej4EZ3ufGGUr=Rf1X=hufmKtPLQH3y4x0kK4nNg5U0w@mail.gmail.com>
2016-10-28 16:15   ` [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value Gianfranco Costamagna
2016-10-28 20:41     ` Arend Van Spriel
2016-11-14 11:22       ` Arend Van Spriel
2016-11-14 11:34         ` Gianfranco Costamagna [this message]
2016-11-14 11:36           ` Arend Van Spriel
2016-11-14 11:47             ` Gianfranco Costamagna
2016-11-15 11:10               ` Kalle Valo
2016-11-15 13:13                 ` Gianfranco Costamagna
2016-11-15 13:18                   ` Nicola Smaldone
2016-11-15 13:21                     ` R: " Arlone Marco
2016-11-15 13:52                   ` Kalle Valo
2016-11-16 10:38                 ` Arend Van Spriel

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=233918815.6357602.1479123253455@mail.yahoo.com \
    --to=locutusofborg@debian.org \
    --cc=Marco.Arlone@roj.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nsmaldone@tierratelematics.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