From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
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, stable@vger.kernel.org
Subject: Re: [PATCH 5.10 0/2] 5.10.1-rc1 review
Date: Tue, 15 Dec 2020 10:29:19 +0100 [thread overview]
Message-ID: <X9iB76jgh/WeLVDI@kroah.com> (raw)
In-Reply-To: <a1bff7f4-f6e9-506c-2c9f-5e7feba90acb@nvidia.com>
On Tue, Dec 15, 2020 at 09:20:26AM +0000, Jon Hunter wrote:
> Hi Greg,
>
> On 14/12/2020 17:06, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.1 release.
> > There are 2 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 Monday, 14 Dec 2020 18:04:42 +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.1-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-5.10.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
>
> Test results for stable-v5.10:
> 15 builds: 15 pass, 0 fail
> 26 boots: 26 pass, 0 fail
> 64 tests: 63 pass, 1 fail
>
> Linux version: 5.10.1-g841fca5a32cc
> Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
> tegra194-p2972-0000, tegra20-ventana,
> tegra210-p2371-2180, tegra210-p3450-0000,
> tegra30-cardhu-a04
>
> Test failures: tegra194-p2972-0000: boot.py
>
>
> Some changes in v5.10 exposed a minor issue in the kernel that can cause
> a blank line warning to be seen. The above test is failing due to this
> blank warning. Thierry has posted a fix for this [0] and should be
> merged for v5.11. It was not tagged for stable, but if you OK to pull
> this in once in the mainline I can send a request. Otherwise all looks
> good, so ...
>
> Tested-by: Jon Hunter <jonathanh@nvidia.com>
Thanks for testing this, and yes, I'll be glad to take this once it hits
Linus's tree, just let me know the git commit id of it there.
thanks,
greg k-h
next prev parent reply other threads:[~2020-12-15 9:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 17:06 [PATCH 5.10 0/2] 5.10.1-rc1 review Greg Kroah-Hartman
2020-12-14 17:06 ` [PATCH 5.10 1/2] Revert "md: change mddev chunk_sectors from int to unsigned" Greg Kroah-Hartman
2020-12-14 17:06 ` [PATCH 5.10 2/2] Revert "dm raid: fix discard limits for raid1 and raid10" Greg Kroah-Hartman
2020-12-14 22:20 ` [PATCH 5.10 0/2] 5.10.1-rc1 review Shuah Khan
2020-12-15 9:24 ` Greg Kroah-Hartman
2020-12-15 9:20 ` Jon Hunter
2020-12-15 9:29 ` Greg Kroah-Hartman [this message]
2020-12-15 10:20 ` Naresh Kamboju
2020-12-15 10:27 ` Greg Kroah-Hartman
2020-12-15 20:32 ` Guenter Roeck
2020-12-16 9:47 ` 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=X9iB76jgh/WeLVDI@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.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).