On Wed, Jun 04, 2025 at 12:23:52PM +0200, Francesco Dolcini wrote:
On Wed, Jun 04, 2025 at 10:39:09AM +0200, Greg Kroah-Hartman wrote:
On Tue, Jun 03, 2025 at 10:33:54PM +0200, Francesco Dolcini wrote:
Hello Greg, Sasha
On Tue, May 27, 2025 at 06:20:23PM +0200, Greg Kroah-Hartman wrote:
6.12-stable review patch. If anyone has any objections, please let me know.
From: Jeff Chen jeff.chen_1@nxp.com
[ Upstream commit 4fcfcbe457349267fe048524078e8970807c1a5b ]
This patch addresses an issue where, despite the AP supporting 40MHz bandwidth, the connection was limited to 20MHz. Without this fix, even if the access point supports 40MHz, the bandwidth after connection remains at 20MHz. This issue is not a regression.
Signed-off-by: Jeff Chen jeff.chen_1@nxp.com Reviewed-by: Francesco Dolcini francesco.dolcini@toradex.com Link: https://patch.msgid.link/20250314094238.2097341-1-jeff.chen_1@nxp.com Signed-off-by: Johannes Berg johannes.berg@intel.com Signed-off-by: Sasha Levin sashal@kernel.org
Can you please drop this patch from any additional stable kernel update? It seems that on 6.12.y it introduced a regression, we are currently investigating it and we'll eventually send a revert for 6.12.y.
This is already in the following released kernels: 6.12.31 6.14.9 6.15 I'll be glad to queue up the revert when it hits Linus's tree. Is that planned anytime soon?
mainline is not affected, the issues seems specific of the backport on 6.12 (6.14 not tested yet), therefore I do not expect any revert in Linus tree.
So 6.15 is not an issue either?
I am looking into the details now, to be sure about my finding, I'll confirm you in the next few days.
If you prefer to not wait, given that this fix was just improving the performance of a specific use case, you can just revert from 6.12.y and 6.14.y.
And 6.15? I'd prefer if you submit the revert as that way it can contain the relevant information about why the revert is only needed in the stable kernel(s) and not also in Linus's tree.
thanks,
greg k-h