From: Kalle Valo <kvalo@codeaurora.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Wright Feng <wright.feng@cypress.com>,
Johannes Berg <johannes.berg@intel.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com
Subject: Re: [PATCH] wireless: brcmfmac: cfg80211: Fix check for ISO3166 code
Date: Thu, 15 Mar 2018 11:15:18 +0200 [thread overview]
Message-ID: <87o9jp7l95.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1521054179-4030-1-git-send-email-stefan.wahren@i2se.com> (Stefan Wahren's message of "Wed, 14 Mar 2018 20:02:59 +0100")
Stefan Wahren <stefan.wahren@i2se.com> writes:
> The commit "regulatory: add NUL to request alpha2" increases the length of
> alpha2 to 3. This causes a regression on brcmfmac, because
> brcmf_cfg80211_reg_notifier() expect valid ISO3166 codes in the complete
> array. So fix this accordingly.
>
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
Arend, the first release for 657308f73e67 is v4.16-rc3 so should this go
to v4.16 as well?
And "wireless:" in the title is useless, I can remove that.
--
Kalle Valo
next prev parent reply other threads:[~2018-03-15 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 19:02 [PATCH] wireless: brcmfmac: cfg80211: Fix check for ISO3166 code Stefan Wahren
2018-03-14 21:43 ` Franky Lin
2018-03-15 6:27 ` Rafał Miłecki
2018-03-15 7:57 ` Stefan Wahren
2018-03-15 9:13 ` Kalle Valo
2018-03-15 9:15 ` Kalle Valo [this message]
2018-03-15 9:27 ` Arend van Spriel
2018-03-15 9:30 ` Kalle Valo
2018-03-15 9:33 ` Arend van Spriel
2018-03-20 10:08 ` brcmfmac: " Kalle Valo
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=87o9jp7l95.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=wright.feng@cypress.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).