From: Andrei Rabusov <a.rabusov@tum.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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,
stable@vger.kernel.org
Subject: Re: [PATCH 5.10 000/219] 5.10.27-rc2 review
Date: Tue, 30 Mar 2021 15:04:18 +0200 [thread overview]
Message-ID: <YGMh0t1iMOP8uqe9@endor.yaviniv> (raw)
In-Reply-To: <20210329101340.196712908@linuxfoundation.org>
On Mon, Mar 29, 2021 at 12:14:07PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.27 release.
> There are 219 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, 31 Mar 2021 10:13: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/v5.x/stable-review/patch-5.10.27-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-5.10.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
I found no problems with 5.10.27-rc2 on my i686, gcc 10.2
Selftest results [ok/not ok]: [1437/80]
Improvement (compared with -rc1): rtctest.1 now is ok:
$ grep rtctest ../log/5.10.27/rc2/selftests.log | grep ok
ok 1 selftests: rtc: rtctest
$ grep rtctest ../log/5.10.27/rc1/selftests.log | grep ok
not ok 1 selftests: rtc: rtctest # TIMEOUT 90 seconds
Tested-by: Andrei Rabusov <a.rabusov@tum.de>
prev parent reply other threads:[~2021-03-30 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 10:14 [PATCH 5.10 000/219] 5.10.27-rc2 review Greg Kroah-Hartman
2021-03-29 17:49 ` Florian Fainelli
2021-03-29 21:34 ` Guenter Roeck
2021-03-30 0:57 ` Samuel Zou
2021-03-30 1:26 ` Shuah Khan
2021-03-30 5:39 ` Naresh Kamboju
2021-03-30 13:04 ` Andrei Rabusov [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=YGMh0t1iMOP8uqe9@endor.yaviniv \
--to=a.rabusov@tum.de \
--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@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;
as well as URLs for NNTP newsgroup(s).