From: Sasha Levin <sashal@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.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,
f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
allen.lkml@gmail.com, broonie@kernel.org,
linux-tegra@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 6.10 000/482] 6.10.14-rc1 review
Date: Wed, 9 Oct 2024 17:59:19 -0400 [thread overview]
Message-ID: <Zwb8t7ngmnVYV9_m@sashalap> (raw)
In-Reply-To: <50b64beb-ba52-4238-a916-33f825c751d9@rnnvmail201.nvidia.com>
On Wed, Oct 09, 2024 at 07:58:55AM -0700, Jon Hunter wrote:
>On Tue, 08 Oct 2024 14:01:03 +0200, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 6.10.14 release.
>> There are 482 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 Thu, 10 Oct 2024 11:55:15 +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.10.14-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.10.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>
>All tests passing for Tegra ...
>
>Test results for stable-v6.10:
> 10 builds: 10 pass, 0 fail
> 26 boots: 26 pass, 0 fail
> 116 tests: 116 pass, 0 fail
>
>Linux version: 6.10.14-rc1-gd44129966591
>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
>
>Tested-by: Jon Hunter <jonathanh@nvidia.com>
Did this one not fail on the same cgroup issue as 6.11? we had the
offending commit in all trees.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-10-09 21:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 12:01 [PATCH 6.10 000/482] 6.10.14-rc1 review Greg Kroah-Hartman
2024-10-08 16:05 ` Peter Schneider
2024-10-08 17:25 ` Mark Brown
2024-10-08 18:16 ` Florian Fainelli
2024-10-08 22:03 ` Shuah Khan
2024-10-09 6:22 ` Naresh Kamboju
2024-10-09 11:35 ` Anders Roxell
2024-10-09 11:53 ` [LTP] " Cyril Hrubis
2024-10-09 12:03 ` Jan Stancek
2024-10-09 22:03 ` Sasha Levin
2024-10-09 14:58 ` Jon Hunter
2024-10-09 21:59 ` Sasha Levin [this message]
2024-10-10 10:40 ` Jon Hunter
2024-10-10 12:13 ` Jon Hunter
2024-10-10 0:04 ` Ron Economos
2024-10-10 8:58 ` Muhammad Usama Anjum
2024-10-10 17:18 ` Peter Schneider
2024-10-10 11:16 ` Miguel Ojeda
2024-10-11 16:22 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zwb8t7ngmnVYV9_m@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox