From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
Angus Ainslie <angus@akkea.ca>, Kalle Valo <kvalo@kernel.org>,
kernel@puri.sm, linux-wireless@vger.kernel.org,
brcm80211@lists.linux.dev, brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] wifi: brcmfmac: use ISO3166 country code fallback on 43752
Date: Sun, 15 Nov 2026 22:06:46 +0100 [thread overview]
Message-ID: <20261115210646.889090-1-arend.vanspriel@broadcom.com> (raw)
In-Reply-To: <20261018-brcmfmac-country-code-v1-1-54d7cbcce035@puri.sm>
On Sun, 18 Oct 2026 08:52:43 +0200, Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm> wrote:
> Without this, the interface stays confined to the country set by
> ccode iovar default value, which is usually 0 (global).
>
> Tested by verifying that enabling the fallback makes channel 13 APs
> visible in scans while in Poland without having to manually change
> the ccode variable.
>
> Fixes: d2587c57ffd8 ("brcmfmac: add 43752 SDIO ids and initialization")
> Cc: stable@vger.kernel.org
> Signed-off-by: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 1 +
> 1 file changed, 1 insertion(+)
The subject does not indicate that this should go in the wireless tree
so wireless-next is assumed. The Fixes: and stable Cc: suggest this should
go in wireless tree and it does not apply to wireless-next tree. Please
clarify and send a v2 with [PATCH wireless] in the subject.
Regards,
Arend
prev parent reply other threads:[~2026-11-15 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 6:52 Sebastian Krzyszkowiak
2026-11-15 21:06 ` Arend van Spriel [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=20261115210646.889090-1-arend.vanspriel@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=angus@akkea.ca \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=kernel@puri.sm \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sebastian.krzyszkowiak@puri.sm \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®