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>,
<linux-tegra@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 6.1 000/600] 6.1.53-rc1 review
Date: Tue, 12 Sep 2023 08:10:29 -0700 [thread overview]
Message-ID: <c90c1139-e99b-4996-87c5-affdf7c6768f@rnnvmail201.nvidia.com> (raw)
In-Reply-To: <20230911134633.619970489@linuxfoundation.org>
On Mon, 11 Sep 2023 15:40:33 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.53 release.
> There are 600 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, 13 Sep 2023 13:44:56 +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.1.53-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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
All tests passing for Tegra ...
Test results for stable-v6.1:
11 builds: 11 pass, 0 fail
28 boots: 28 pass, 0 fail
116 tests: 116 pass, 0 fail
Linux version: 6.1.53-rc1-g6e71673725ca
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>
Jon
next prev parent reply other threads:[~2023-09-12 15:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 13:40 Greg Kroah-Hartman
2023-09-11 13:42 ` [PATCH 6.1 102/600] eventfd: prevent underflow for eventfd semaphores Greg Kroah-Hartman
2023-09-11 20:13 ` [PATCH 6.1 000/600] 6.1.53-rc1 review Shuah Khan
2023-09-11 20:58 ` Daniel Díaz
2023-09-12 2:25 ` Daniel Díaz
2023-09-12 8:49 ` Naresh Kamboju
2023-09-12 9:03 ` Greg Kroah-Hartman
2023-09-12 10:32 ` Greg Kroah-Hartman
2023-09-12 11:56 ` Naresh Kamboju
2023-09-12 12:01 ` Greg Kroah-Hartman
2023-09-13 13:55 ` Naresh Kamboju
2023-09-12 5:50 ` Bagas Sanjaya
2023-09-12 9:00 ` Sudip Mukherjee (Codethink)
2023-09-12 9:03 ` Naresh Kamboju
2023-09-12 10:27 ` Takeshi Ogasawara
2023-09-12 12:37 ` Conor Dooley
2023-09-12 15:10 ` Jon Hunter [this message]
2023-09-12 17:35 ` Florian Fainelli
2023-09-12 18:35 ` Guenter Roeck
2023-09-13 2:40 ` Ron Economos
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=c90c1139-e99b-4996-87c5-affdf7c6768f@rnnvmail201.nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®