From: Samuel Zou <zou_wei@huawei.com>
To: <gregkh@linuxfoundation.org>, <linux-kernel@vger.kernel.org>
Cc: <torvalds@linux-foundation.org>, <akpm@linux-foundation.org>,
<linux@roeck-us.net>, <shuah@kernel.org>,
<lkft-triage@lists.linaro.org>, <patches@kernelci.org>,
<pavel@denx.de>, <jonathanh@nvidia.com>, <f.fainelli@gmail.com>,
<stable@vger.kernel.org>, <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 5.10 000/657] 5.10.20-rc4 review
Date: Fri, 5 Mar 2021 17:07:42 +0800 [thread overview]
Message-ID: <da58faaa-e0f4-c0f4-d68c-7c1c09415b58@huawei.com> (raw)
In-Reply-To: <1eca83a8a33c44f99ed11d3b423505df@HQMAIL107.nvidia.com>
On Tue, 02 Mar 2021 20:28:49 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.20 release.
> There are 657 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, 04 Mar 2021 19:25:07 +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/v5.x/stable-review/patch-5.10.20-rc4.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Tested on arm64 and x86 for 5.10.20,
Kernel repo:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Branch: linux-5.10.y
Version: 5.10.20
Commit: 83be32b6c9e55d5b04181fc9788591d5611d4a96
Compiler: gcc version 7.3.0 (GCC)
arm64 (No kernel failures)
--------------------------------------------------------------------
Testcase Result Summary:
total_num: 4716
succeed_num: 4713
failed_num: 3
timeout_num: 0
x86 (No kernel failures)
--------------------------------------------------------------------
Testcase Result Summary:
total_num: 4716
succeed_num: 4713
failed_num: 3
timeout_num: 0
Tested-by: Hulk Robot <hulkci@huawei.com>
next parent reply other threads:[~2021-03-05 9:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1eca83a8a33c44f99ed11d3b423505df@HQMAIL107.nvidia.com>
2021-03-05 9:07 ` Samuel Zou [this message]
2021-03-05 10:15 ` [PATCH 5.10 000/657] 5.10.20-rc4 review Greg KH
2021-03-02 19:28 Greg Kroah-Hartman
2021-03-02 21:31 ` Pavel Machek
2021-03-02 22:12 ` Florian Fainelli
2021-03-03 10:18 ` Guillaume Tucker
2021-03-04 10:40 ` Greg Kroah-Hartman
2021-03-03 16:12 ` Naresh Kamboju
2021-03-03 20:04 ` Guenter Roeck
2021-03-04 17:56 ` Naresh Kamboju
2021-03-04 21:14 ` Linus Torvalds
2021-03-05 8:09 ` Naresh Kamboju
2021-03-05 8:52 ` Greg Kroah-Hartman
2021-03-05 10:02 ` Naresh Kamboju
2021-03-05 10:10 ` Greg Kroah-Hartman
2021-03-03 20:08 ` Guenter Roeck
2021-03-04 10:40 ` Greg Kroah-Hartman
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=da58faaa-e0f4-c0f4-d68c-7c1c09415b58@huawei.com \
--to=zou_wei@huawei.com \
--cc=akpm@linux-foundation.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=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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