On Fri, Aug 16, 2024 at 08:12:36PM +0000, Jon Hunter wrote: > > ________________________________ > From: Jon Hunter <jonathanh@xxxxxxxxxx> > Sent: Friday, August 16, 2024 2:43 PM > To: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>; patches@xxxxxxxxxxxxxxx <patches@xxxxxxxxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx <linux-kernel@xxxxxxxxxxxxxxx>; torvalds@xxxxxxxxxxxxxxxxxxxx <torvalds@xxxxxxxxxxxxxxxxxxxx>; akpm@xxxxxxxxxxxxxxxxxxxx <akpm@xxxxxxxxxxxxxxxxxxxx>; linux@xxxxxxxxxxxx <linux@xxxxxxxxxxxx>; shuah@xxxxxxxxxx <shuah@xxxxxxxxxx>; patches@xxxxxxxxxxxx <patches@xxxxxxxxxxxx>; lkft-triage@xxxxxxxxxxxxxxxx <lkft-triage@xxxxxxxxxxxxxxxx>; pavel@xxxxxxx <pavel@xxxxxxx>; Jon Hunter <jonathanh@xxxxxxxxxx>; f.fainelli@xxxxxxxxx <f.fainelli@xxxxxxxxx>; sudipm.mukherjee@xxxxxxxxx <sudipm.mukherjee@xxxxxxxxx>; srw@xxxxxxxxxxxxxxxx <srw@xxxxxxxxxxxxxxxx>; rwarsow@xxxxxx <rwarsow@xxxxxx>; conor@xxxxxxxxxx <conor@xxxxxxxxxx>; allen.lkml@xxxxxxxxx <allen.lkml@xxxxxxxxx>; broonie@xxxxxxxxxx <broonie@xxxxxxxxxx>; linux-tegra@xxxxxxxxxxxxxxx <linux-tegra@xxxxxxxxxxxxxxx>; stable@xxxxxxxxxxxxxxx <stable@xxxxxxxxxxxxxxx> > Subject: Re: [PATCH 5.10 000/350] 5.10.224-rc2 review > > On Fri, 16 Aug 2024 12:22:05 +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.10.224 release. > > There are 350 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 Sun, 18 Aug 2024 10:14:04 +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.224-rc2.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. > > > > thanks, > > > > greg k-h > > Failures detected for Tegra ... > > Test results for stable-v5.10: > 10 builds: 10 pass, 0 fail > 31 boots: 26 pass, 5 fail > 45 tests: 44 pass, 1 fail > > Linux version: 5.10.224-rc2-g470450f8c61c > Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, > tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000, > tegra20-ventana, tegra210-p2371-2180, > tegra210-p3450-0000, tegra30-cardhu-a04 > > Boot failures: tegra186-p2771-0000, tegra210-p2371-2180, > tegra210-p3450-0000 > > Test failures: tegra194-p2972-0000: boot.py > > --- > > Apologies for the mail formatting. I am travelling and only have outlook for mobile :-( > > Bisect points to the following commit ... > > # first bad commit: [4bade5a6b1cfe81c9777aa3c8823009ff28a6e7f] memory: fsl_ifc: Make FSL_IFC config visible and selectable > > Reverting this does fix the issue. Seems odd but this appears to disable CONFIG_MEMORY for v5.10 with ARM64 defconfig. So something we need to fix. Ah, that's a mess. I'll go drop this one for now, glad it's not showing up on 5.15.y where this commit also is. It's not really important for 5.10.y so there's no harm in removing it. thanks, greg k-h
