Re: [PATCH] wifi: brcmfmac: set F2 blocksize to 256 for BCM43752
Arend van Spriel <[email protected]> Tue, 14 Jul 2026 19:03:13 +0200
| Newsgroups | dev.linux.lists.brcm80211,org.kernel.vger.linux-kernel,org.kernel.vger.linux-wireless,org.kernel.vger.stable |
|---|---|
| Message-ID | <[email protected]> |
Op 14 juli 2026 04:29:16 schreef LiangCheng Wang <[email protected]>: > Hi Arend, > > On 13/07/2026 12:51, Arend van Spriel wrote: >> Looks good to me but the stable instruction looks confusion. What do you >> mean. If there is no 43752 support there is no need for this patch, right? > > Thank you for the review, and thanks Gokul for the detailed > explanation - that is exactly what I meant, and sorry the annotation > was not clearer. To summarize: 43752 support has been present since > v5.15 (commit d2587c57ffd8 ("brcmfmac: add 43752 SDIO ids and > initialization")), under the SDIO_DEVICE_ID_BROADCOM_CYPRESS_43752 id > name. Commit 74e2ef72bd4b ("wifi: brcmfmac: fix 43752 SDIO FWVID > incorrectly labelled as Cypress (CYW)"), which landed in v6.18, > renamed it to SDIO_DEVICE_ID_BROADCOM_43752. > > I also have to correct myself here: the boundary in the annotation > should have been "<= 6.17" rather than "<= 6.16", since the rename > only landed in v6.18. Apologies for the extra confusion. > > Gokul's suggestion of cherry-picking the rename patch together with > this one into the stable trees sounds cleaner to me than editing the > id name while backporting, so I would be glad to go with that. > > If it helps, I would be happy to send a v2 with the stable annotation > in the prerequisite format from > Documentation/process/stable-kernel-rules.rst: > > Cc: <[email protected]> # 74e2ef72bd4b: wifi: brcmfmac: fix 43752 SDIO > FWVID incorrectly labelled as Cypress (CYW) > > Please let me know if you would prefer that, or if the patch is fine > to take as is. Cc: instructions to stable should stick to the stable-kernel-rules format if possible. I suspect there is a bit of scripting sifting through it. Regards, Arend > Best regards, > LiangCheng