From: Jon Hunter <jonathanh@nvidia.com>
To: Pavel Machek <pavel@denx.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<torvalds@linux-foundation.org>, <akpm@linux-foundation.org>,
<linux@roeck-us.net>, <shuah@kernel.org>, <patches@kernelci.org>,
<lkft-triage@lists.linaro.org>, <f.fainelli@gmail.com>,
<stable@vger.kernel.org>, <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 5.10 000/593] 5.10.50-rc1 review
Date: Mon, 12 Jul 2021 10:42:23 +0100 [thread overview]
Message-ID: <028eb5b4-c0bb-d4a6-5e06-ad508cebd0cf@nvidia.com> (raw)
In-Reply-To: <20210712093526.GA23916@duo.ucw.cz>
On 12/07/2021 10:35, Pavel Machek wrote:
> Hi!
>
> (2000 lines trimmed)
>
>>> tools/testing/selftests/vm/protection_keys.c | 12 +-
>>> 638 files changed, 5205 insertions(+), 2782 deletions(-)
>
>> All tests passing for Tegra ...
>>
>> Test results for stable-v5.10:
>> 10 builds: 10 pass, 0 fail
>> 28 boots: 28 pass, 0 fail
>> 70 tests: 70 pass, 0 fail
>>
>> Linux version: 5.10.50-rc1-g3e2628c73ba0
>> Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
>> tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
>> tegra20-ventana, tegra210-p2371-2180,
>> tegra210-p3450-0000, tegra30-cardhu-a04
>>
>> Tested-by: Jon Hunter <jonathanh@nvidia.com>
>
> Thanks for testing... but could we get you to snip the parts of email
> not important for the reply?
Yes I have noticed that too! The script we have use to trim that, so I
need to see why it no longer is. I have recently made some modifications
and so clearly have broken that. Anyway, I will get that fixed.
Jon
--
nvpublic
next prev parent reply other threads:[~2021-07-12 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210712060843.180606720@linuxfoundation.org>
2021-07-12 9:18 ` [PATCH 5.10 000/593] 5.10.50-rc1 review Jon Hunter
2021-07-12 9:35 ` Pavel Machek
2021-07-12 9:42 ` Jon Hunter [this message]
2021-07-12 13:15 ` Jon Hunter
2021-07-12 13:13 ` Jon Hunter
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=028eb5b4-c0bb-d4a6-5e06-ad508cebd0cf@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.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