Linux wireless drivers development
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: "Vinícius Ramon Fontanela" <vfontanela@gmail.com>
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
	brcm80211-dev-list.pdl@broadcom.com,
	Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [PATCH v2] wifi: brcmfmac: allow ISO3166 fallback for BCM4350
Date: Sun,  4 Oct 2026 02:45:19 -0700	[thread overview]
Message-ID: <20261004094519.1323940-1-arend.vanspriel@broadcom.com> (raw)
In-Reply-To: <20260915174300.28363-1-vfontanela@gmail.com>

On Tue, 15 Sep 2026 14:43:00 -0300, Vinícius Ramon Fontanela wrote:
> BCM4350 devices using brcmfmac on x86/PCIe may have no platform-provided
> country code map. In that case brcmf_translate_country_code() falls back to
> ISO3166 codes only for chips accepted by
> brmcf_use_iso3166_ccode_fallback().
> 
> BCM4350 is currently missing from that list, despite the adjacent BCM4345
> and BCM4356 being present. Add BCM4350 so these devices can use the ISO3166
> country code with revision 0.

Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>

> Signed-off-by: Vinícius Ramon Fontanela <vfontanela@gmail.com>
> ---
>  drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 1 +
>  1 file changed, 1 insertion(+)

      reply	other threads:[~2026-10-04  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 18:49 [PATCH] wifi: brcmfmac: allow ISO3166 fallback for BCM4350 Vinícius Ramon Fontanela
2026-09-14 20:03 ` Arend van Spriel
2026-09-15 17:43   ` [PATCH v2] " Vinícius Ramon Fontanela
2026-10-04  9:45     ` 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=20261004094519.1323940-1-arend.vanspriel@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vfontanela@gmail.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