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@denx.de>,
<jonathanh@nvidia.com>, <f.fainelli@gmail.com>,
<sudipm.mukherjee@gmail.com>, <srw@sladewatkins.net>,
<rwarsow@gmx.de>, <conor@kernel.org>, <hargar@microsoft.com>,
<broonie@kernel.org>, <linux-tegra@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH 6.15 000/263] 6.15.5-rc2 review
Date: Mon, 7 Jul 2025 01:43:32 -0700 [thread overview]
Message-ID: <19d2e833-547d-4712-a68d-b64cb3438999@drhqmail203.nvidia.com> (raw)
In-Reply-To: <20250704125604.759558342@linuxfoundation.org>
On Fri, 04 Jul 2025 16:44:42 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.15.5 release.
> There are 263 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, 06 Jul 2025 12:55:09 +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.15.5-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-6.15.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
All tests passing for Tegra ...
Test results for stable-v6.15:
10 builds: 10 pass, 0 fail
28 boots: 28 pass, 0 fail
120 tests: 120 pass, 0 fail
Linux version: 6.15.5-rc2-gf6977c36decb
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,
tegra30-cardhu-a04
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Jon
prev parent reply other threads:[~2025-07-07 8:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 14:44 [PATCH 6.15 000/263] 6.15.5-rc2 review Greg Kroah-Hartman
2025-07-04 15:37 ` Ronald Warsow
2025-07-04 21:20 ` Mark Brown
2025-07-05 9:12 ` Luna Jernberg
2025-07-04 22:08 ` Markus Reichelt
2025-07-05 0:03 ` Miguel Ojeda
2025-07-05 0:04 ` Takeshi Ogasawara
2025-07-05 4:20 ` Peter Schneider
2025-07-05 20:46 ` Florian Fainelli
2025-07-05 22:03 ` Achill Gilgenast
2025-07-06 7:04 ` Pascal Ernster
2025-07-06 10:20 ` Naresh Kamboju
2025-07-07 18:34 ` Naresh Kamboju
2025-07-08 21:24 ` Naresh Kamboju
2025-07-09 8:19 ` Greg Kroah-Hartman
2025-07-07 8:43 ` Jon Hunter [this message]
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=19d2e833-547d-4712-a68d-b64cb3438999@drhqmail203.nvidia.com \
--to=jonathanh@nvidia.com \
--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@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;
as well as URLs for NNTP newsgroup(s).