From: Jon Hunter <jonathanh@nvidia.com>
To: Guenter Roeck <linux@roeck-us.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <torvalds@linux-foundation.org>,
<akpm@linux-foundation.org>, <shuah@kernel.org>,
<patches@kernelci.org>, <lkft-triage@lists.linaro.org>,
<pavel@denx.de>, <stable@vger.kernel.org>
Subject: Re: [PATCH 4.14 00/50] 4.14.218-rc1 review
Date: Sat, 30 Jan 2021 13:50:48 +0000 [thread overview]
Message-ID: <6e5abee6-8275-2b15-4ae2-f28c6508f55a@nvidia.com> (raw)
In-Reply-To: <20210129182147.GB146143@roeck-us.net>
On 29/01/2021 18:21, Guenter Roeck wrote:
> On Fri, Jan 29, 2021 at 12:06:25PM +0100, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 4.14.218 release.
>> There are 50 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-v4.14:
8 builds: 8 pass, 0 fail
16 boots: 16 pass, 0 fail
30 tests: 30 pass, 0 fail
Linux version: 4.14.218-rc1-g672a9e33037f
Boards tested: tegra124-jetson-tk1, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a04
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Jon
--
nvpublic
next prev parent reply other threads:[~2021-01-30 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210129105913.476540890@linuxfoundation.org>
2021-01-29 11:06 ` [PATCH 4.14 10/50] xen: Fix event channel callback via INTX/GSI Greg Kroah-Hartman
2021-01-29 18:21 ` [PATCH 4.14 00/50] 4.14.218-rc1 review Guenter Roeck
2021-01-30 13:50 ` Jon Hunter [this message]
2021-01-30 6:44 ` Naresh Kamboju
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=6e5abee6-8275-2b15-4ae2-f28c6508f55a@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=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).