[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d770359-38b4-4fc5-a15e-6b5bce079b9a@nvidia.com>
Date: Tue, 23 Jan 2024 16:11:52 +0000
From: Jon Hunter <jonathanh@...dia.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, pavel@...x.de, f.fainelli@...il.com,
sudipm.mukherjee@...il.com, srw@...dewatkins.net, rwarsow@....de,
conor@...nel.org, allen.lkml@...il.com, linux-tegra@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH 6.7 000/641] 6.7.2-rc1 review
On 23/01/2024 16:10, Jon Hunter wrote:
> On Mon, 22 Jan 2024 15:48:24 -0800, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 6.7.2 release.
>> There are 641 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, 24 Jan 2024 23:56:49 +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/v6.x/stable-review/patch-6.7.2-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-6.7.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>
> Failures detected for Tegra ...
>
> Test results for stable-v6.7:
> 10 builds: 10 pass, 0 fail
> 28 boots: 26 pass, 2 fail
> 96 tests: 95 pass, 1 fail
>
> Linux version: 6.7.2-rc1-g8538581d9e8e
> 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: tegra210-p2371-2180
This is a new regression for linux-6.7.y. See linux-5.15.y report.
> Test failures: tegra186-p2771-0000: pm-system-suspend.sh
This one is a known issue for mainline v6.7.
Jon
--
nvpublic
Powered by blists - more mailing lists