From: Kalle Valo <kvalo@codeaurora.org>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: "Rafał Miłecki" <rafal@milecki.pl>,
"Arend van Spriel" <aspriel@gmail.com>,
"Franky Lin" <franky.lin@broadcom.com>,
"Hante Meuleman" <hante.meuleman@broadcom.com>,
"Chi-hsien Lin" <chi-hsien.lin@infineon.com>,
"Wright Feng" <wright.feng@infineon.com>,
"Chung-hsien Hsu" <chung-hsien.hsu@infineon.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com,
"Shawn Guo" <shawn.guo@linaro.org>
Subject: Re: [PATCH] brcmfmac: use ISO3166 country code and 0 rev as fallback
Date: Tue, 15 Jun 2021 10:36:28 +0000 (UTC) [thread overview]
Message-ID: <20210615103628.4211BC43460@smtp.codeaurora.org> (raw)
In-Reply-To: <20210425110200.3050-1-shawn.guo@linaro.org>
Shawn Guo <shawn.guo@linaro.org> wrote:
> Instead of aborting country code setup in firmware, use ISO3166 country
> code and 0 rev as fallback, when country_codes mapping table is not
> configured. This fallback saves the country_codes table setup for recent
> brcmfmac chipsets/firmwares, which just use ISO3166 code and require no
> revision number.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
Patch applied to wireless-drivers-next.git, thanks.
b0b524f079a2 brcmfmac: use ISO3166 country code and 0 rev as fallback
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210425110200.3050-1-shawn.guo@linaro.org/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-06-15 10:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 11:02 [PATCH] brcmfmac: use ISO3166 country code and 0 rev as fallback Shawn Guo
2021-04-28 12:03 ` Arend van Spriel
2021-04-28 12:42 ` Shawn Guo
2021-05-23 6:12 ` Shawn Guo
2021-05-23 6:54 ` Arend Van Spriel
2021-06-15 10:36 ` Kalle Valo [this message]
2021-09-07 19:22 ` [BUG] " Soeren Moch
2021-09-08 1:00 ` Shawn Guo
2021-09-08 5:08 ` Soeren Moch
2021-09-09 2:20 ` Shawn Guo
2021-09-09 8:39 ` Soeren Moch
2021-09-12 1:51 ` Shawn Guo
2021-09-21 9:20 ` Kalle Valo
2021-09-26 20:20 ` Soeren Moch
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=20210615103628.4211BC43460@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=chi-hsien.lin@infineon.com \
--cc=chung-hsien.hsu@infineon.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=shawn.guo@linaro.org \
--cc=wright.feng@infineon.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).