Re: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-11-16 Thread Arend Van Spriel
On 15-11-2016 12:10, Kalle Valo wrote: > Gianfranco Costamagna writes: > >>> Well, not before you pointed it out ;-). You are welcome to send a patch >>> fixing it. Otherwise, I will take care of it. >> >> attaching a format-patch like version. >> I don't think we need

Re: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-11-15 Thread Kalle Valo
Gianfranco Costamagna writes: >> Signed-off-by: Nicola Smaldone > >> Signed-off-by: Arlone Marco > >>Please note that you cannot add Signed-off-by for other people without >>their explicit approval (see

R: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-11-15 Thread Arlone Marco
; Arlone Marco Oggetto: RE: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value No problem for me, thanks. Nicola SMALDONE www.tierratelematics.com -Original Message- From: Gianfranco Costamagna [mailto:locutusofb...@debian.org] Sent: martedì 15

RE: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-11-15 Thread Nicola Smaldone
; brcm80211-dev-l...@broadcom.com; linux-wireless@vger.kernel.org; Nicola Smaldone <nsmald...@tierratelematics.com>; marco.arl...@roj.com Subject: Re: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value Hi, > Signed-off-by: Nicola S

Re: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-11-15 Thread Gianfranco Costamagna
Hi, > Signed-off-by: Nicola Smaldone > Signed-off-by: Arlone Marco >Please note that you cannot add Signed-off-by for other people without >their explicit approval (see Documentation/SubmittingPatches). I don't >know if they did it in

Re: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-11-15 Thread Kalle Valo
Gianfranco Costamagna writes: >> Well, not before you pointed it out ;-). You are welcome to send a patch >> fixing it. Otherwise, I will take care of it. > > attaching a format-patch like version. > I don't think we need a Tested-by or whatever, because it is just a

Re: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-11-14 Thread Gianfranco Costamagna
Hi Arend, >Well, not before you pointed it out ;-). You are welcome to send a patch >fixing it. Otherwise, I will take care of it. attaching a format-patch like version. I don't think we need a Tested-by or whatever, because it is just a typo in a comment. (this is my first contribution,

Re: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-11-14 Thread Gianfranco Costamagna
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

Re: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-11-14 Thread Arend Van Spriel
On 14-11-2016 12:34, Gianfranco Costamagna wrote: > 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

Re: [PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-11-14 Thread Arend Van Spriel
On 28-10-2016 22:41, Arend Van Spriel wrote: > On 28-10-2016 18:15, Gianfranco Costamagna wrote: >> (resending from my debian.org mail address, to avoid spam filtering) >> >> Hi Broadcom developers and linux wireless list. >> >> We found a possible issue in the cfg80211 implementation of the

[PATCH] broadcom/brcm80211/brcmfmac/cfg80211 driver, bad regulatory domain frequency value

2016-10-28 Thread Gianfranco Costamagna
(resending from my debian.org mail address, to avoid spam filtering) Hi Broadcom developers and linux wireless list. We found a possible issue in the cfg80211 implementation of the regulatory domain rules: .reg_rules = { /* IEEE 802.11b/g, channels 1..11 */