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 4.19 000/246] 4.19.178-rc4 review
Date: Fri, 5 Mar 2021 17:08:01 +0800 [thread overview]
Message-ID: <6f292dad-0a40-01be-ec5a-cee263ac080a@huawei.com> (raw)
In-Reply-To: <1d172bcc33f44475b8c6737e9b58c439@HQMAIL107.nvidia.com>
On Tue, 02 Mar 2021 20:28:20 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.178 release.
> There are 246 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/v4.x/stable-review/patch-4.19.178-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-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Tested on arm64 and x86 for 4.19.178,
Kernel repo:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Branch: linux-4.19.y
Version: 4.19.178
Commit: dfb571610ba392179348c8472bfb131d4173d585
Compiler: gcc version 7.3.0 (GCC)
arm64:
--------------------------------------------------------------------
Testcase Result Summary:
total_num: 4674
succeed_num: 4674
failed_num: 0
timeout_num: 0
x86 (No kernel failures)
--------------------------------------------------------------------
Testcase Result Summary:
total_num: 4674
succeed_num: 4769
failed_num: 5
timeout_num: 0
Tested-by: Hulk Robot <hulkci@huawei.com>
next prev parent reply other threads:[~2021-03-05 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 19:28 [PATCH 4.19 000/246] 4.19.178-rc4 review Greg Kroah-Hartman
2021-03-02 21:29 ` Pavel Machek
2021-03-03 9:27 ` Jon Hunter
2021-03-05 9:08 ` Samuel Zou [this message]
2021-03-03 14:55 ` Naresh Kamboju
2021-03-03 15:08 ` Naresh Kamboju
2021-03-03 20:07 ` Guenter Roeck
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=6f292dad-0a40-01be-ec5a-cee263ac080a@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