From: Jon Hunter <jonathanh@nvidia.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>, <patches@kernelci.org>,
<lkft-triage@lists.linaro.org>,
linux-stable <stable@vger.kernel.org>, <pavel@denx.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH 5.10 00/32] 5.10.12-rc1 review
Date: Sat, 30 Jan 2021 13:50:32 +0000 [thread overview]
Message-ID: <980a1226-4ebb-cd29-c020-1fcbe8517ca8@nvidia.com> (raw)
In-Reply-To: <CA+G9fYsEseDKySENMfSiRMgh-CTefpCtsQsBFbJ6tfmRoBPxwA@mail.gmail.com>
On 29/01/2021 18:22, Naresh Kamboju wrote:
> On Fri, 29 Jan 2021 at 16:47, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>>
>> This is the start of the stable review cycle for the 5.10.12 release.
>> There are 32 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.
Replying here because I don't have the original.
Test results for stable-v5.10:
12 builds: 12 pass, 0 fail
26 boots: 26 pass, 0 fail
65 tests: 65 pass, 0 fail
Linux version: 5.10.12-rc1-g324e71045b28
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra210-p3450-0000,
tegra30-cardhu-a04
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Jon
--
nvpublic
next prev parent reply other threads:[~2021-01-30 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210129105912.628174874@linuxfoundation.org>
2021-01-29 18:22 ` Naresh Kamboju
2021-01-30 13:01 ` Greg Kroah-Hartman
2021-01-30 13:50 ` Jon Hunter [this message]
2021-01-29 18:23 ` Guenter Roeck
2021-01-30 13:01 ` Greg Kroah-Hartman
[not found] ` <20210129125914.GA23853@duo.ucw.cz>
2021-01-30 13:00 ` 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=980a1226-4ebb-cd29-c020-1fcbe8517ca8@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@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
all inboxes | Powered by JetHome®