Received-SPF: pass (google.com: domain of linux-kernel+bounces-91955-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Tue, 5 Mar 2024 18:05:04 +0900
From: Dominique Martinet <asmadeus@codewreck.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org, pavel@denx.de,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, allen.lkml@gmail.com
Subject: Re: [PATCH 5.10 00/42] 5.10.212-rc1 review
Message-ID: <ZebgQDAotbvxSg-l@codewreck.org>
References: <20240304211537.631764077@linuxfoundation.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20240304211537.631764077@linuxfoundation.org>

Greg Kroah-Hartman wrote on Mon, Mar 04, 2024 at 09:23:27PM +0000:
> This is the start of the stable review cycle for the 5.10.212 release.
> There are 42 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Wed, 06 Mar 2024 21:15:26 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.212-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.

Tested 4b0abedc88b0 ("Linux 5.10.212-rc1") on:
- arm i.MX6ULL (Armadillo 640)
- arm64 i.MX8MP (Armadillo G4)

For some reason the wlan interface didn't come up on the arm32 board
(brcmfmac brought up through usb, mainline driver), which is something I
hadn't observed before, but I've just rebooted a dozen of times and it's
always been up after that *and* I don't see anything in this stable
release that sounds like it could be related so I'll blame it on a
glitch to look further into, and not something related...
(I'll report back again if I find something more convincing, trying to
get a second occurence at least... if I can reproduce I'll confirm it
reproduce on 5.10.211 first then keep digging but it looks like that'll
take a while)

No obvious regression in dmesg or basic tests:
Tested-by: Dominique Martinet <dominique.martinet@atmark-techno.com>


Thanks,
-- 
Dominique