From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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@nabladev.com>,
<jonathanh@nvidia.com>, <f.fainelli@gmail.com>,
<sudipm.mukherjee@gmail.com>, <rwarsow@gmx.de>,
<conor@kernel.org>, <hargar@microsoft.com>, <broonie@kernel.org>,
<achill@achill.org>, <sr@sladewatkins.com>,
<linux-tegra@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 6.12 000/265] 6.12.77-rc1 review
Date: Fri, 13 Mar 2026 09:16:16 -0700 [thread overview]
Message-ID: <bddb3680-e01d-4eb6-b6b3-c7852ad1297e@rnnvmail202.nvidia.com> (raw)
In-Reply-To: <20260312201018.128816016@linuxfoundation.org>
On Thu, 12 Mar 2026 21:06:27 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.12.77 release.
> There are 265 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 Fri, 13 Mar 2026 20:09:29 +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.12.77-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.12.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Failures detected for Tegra ...
Test results for stable-v6.12:
11 builds: 11 pass, 0 fail
28 boots: 28 pass, 0 fail
133 tests: 132 pass, 1 fail
Linux version: 6.12.77-rc1-g92f326b98fe0
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000,
tegra194-p3509-0000+p3668-0000, tegra20-ventana,
tegra210-p2371-2180, tegra210-p3450-0000,
tegra234-p3737-0000+p3701-0000, tegra30-cardhu-a04
Test failures: tegra194-p2972-0000: boot.py
Jon
next prev parent reply other threads:[~2026-03-13 16:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 20:06 Greg Kroah-Hartman
2026-03-12 20:41 ` Brett A C Sheffield
2026-03-13 3:25 ` Shuah Khan
2026-03-13 5:32 ` freeze during boot regression " Barry K. Nathan
2026-03-13 5:55 ` Barry K. Nathan
2026-03-13 6:10 ` Ron Economos
2026-03-13 7:27 ` Francesco Dolcini
2026-03-13 8:05 ` Barry K. Nathan
2026-03-13 9:37 ` Ron Economos
2026-03-13 10:53 ` Barry K. Nathan
2026-03-13 13:38 ` Barry K. Nathan
2026-03-13 13:49 ` Greg Kroah-Hartman
2026-03-13 13:05 ` Mark Brown
2026-03-13 16:16 ` Jon Hunter [this message]
2026-03-13 16:18 ` Jon Hunter
2026-03-13 17:02 ` Florian Fainelli
2026-03-13 21:10 ` Miguel Ojeda
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=bddb3680-e01d-4eb6-b6b3-c7852ad1297e@rnnvmail202.nvidia.com \
--to=jonathanh@nvidia.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.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@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--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
all inboxes | Powered by JetHome®