From: John Hubbard <jhubbard@nvidia.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>, Shuah Khan <shuah@kernel.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Ryan Roberts <ryan.roberts@arm.com>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Alexandre Ghiti <alex@ghiti.fr>
Subject: Re: [PATCH] selftests: Fix arm64 test installation
Date: Fri, 14 Jul 2023 12:39:24 -0700 [thread overview]
Message-ID: <78861bf4-649f-5cd5-e2be-89f5d19a42d2@nvidia.com> (raw)
In-Reply-To: <d03af9cc-c72e-d23f-73ad-ca0e079c3187@linuxfoundation.org>
On 7/14/23 12:11, Shuah Khan wrote:
...
>> Just to be clear, when you say you're applying "both", I'm hoping you mean
>> both of these:
>>
>>
>> [1] https://lore.kernel.org/all/20230711005629.2547838-1-jhubbard@nvidia.com/
>> [2] https://lore.kernel.org/all/20230712193514.740033-1-jhubbard@nvidia.com/
>>
>
> Right. The ones you have links to:
>
> Please check the latest fixes to see if we are all squared away:
> https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=fixes
>
Yes, the patches have made it into your tree safely, looks good!
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2023-07-14 19:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 14:04 [PATCH] selftests: Fix arm64 test installation Mark Brown
2023-07-10 20:22 ` John Hubbard
2023-07-10 21:20 ` Mark Brown
2023-07-10 21:31 ` John Hubbard
2023-07-10 22:30 ` Mark Brown
2023-07-10 23:10 ` John Hubbard
2023-07-11 14:00 ` Mark Brown
2023-07-13 20:02 ` Shuah Khan
2023-07-13 20:16 ` John Hubbard
2023-07-14 17:48 ` Shuah Khan
2023-07-14 18:09 ` Mark Brown
2023-07-14 18:19 ` John Hubbard
2023-07-14 18:26 ` Andrew Morton
2023-07-14 18:32 ` Shuah Khan
2023-07-14 18:36 ` John Hubbard
2023-07-14 19:11 ` Shuah Khan
2023-07-14 19:39 ` John Hubbard [this message]
2023-07-18 14:54 ` Mark Brown
2023-07-18 14:56 ` Shuah Khan
2023-07-18 14:57 ` Mark Brown
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=78861bf4-649f-5cd5-e2be-89f5d19a42d2@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=anders.roxell@linaro.org \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=usama.anjum@collabora.com \
/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