From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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,
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 7.1 0000/2077] 7.1.5-rc1 review
Date: Wed, 22 Jul 2026 14:14:53 +0100 [thread overview]
Message-ID: <ecc491e1-6f06-4c7d-b7fc-099713c99a1c@nvidia.com> (raw)
In-Reply-To: <4dbf52af-61a2-4767-8c85-b358cc157812@rnnvmail201.nvidia.com>
On 22/07/2026 14:13, Jon Hunter wrote:
> On Tue, 21 Jul 2026 16:54:33 +0200, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 7.1.5 release.
>> There are 2077 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, 23 Jul 2026 15:23:00 +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/v7.x/stable-review/patch-7.1.5-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-7.1.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>
> All tests passing for Tegra ...
>
> Test results for stable-v7.1:
> 10 builds: 10 pass, 0 fail
> 28 boots: 28 pass, 0 fail
> 158 tests: 158 pass, 0 fail
>
> Linux version: 7.1.5-rc1-g06ed1e6c413d
> 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,
> tegra234-p3768-0000+p3767-0005, tegra30-cardhu-a04
>
> Tested-by: Jon Hunter <jonathanh@nvidia.com>
Ignore this duplicate report.
Jon
--
nvpublic
prev parent reply other threads:[~2026-07-22 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260721152552.646164743@linuxfoundation.org>
2026-07-21 15:00 ` [PATCH 7.1 0345/2077] drm/tegra: fbdev: Do not assign to struct drm_fb_helper.info Greg Kroah-Hartman
[not found] ` <4dbf52af-61a2-4767-8c85-b358cc157812@rnnvmail201.nvidia.com>
2026-07-22 13:14 ` 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=ecc491e1-6f06-4c7d-b7fc-099713c99a1c@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