From: Mark Brown <broonie@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: John Hubbard <jhubbard@nvidia.com>, Shuah Khan <shuah@kernel.org>,
Andrew Morton <akpm@linux-foundation.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
Subject: Re: [PATCH] selftests: Fix arm64 test installation
Date: Fri, 14 Jul 2023 19:09:18 +0100 [thread overview]
Message-ID: <421bebb3-19e9-47a7-8b2b-f69f125df22f@sirena.org.uk> (raw)
In-Reply-To: <620a5b91-9715-ee28-423c-851506b10832@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On Fri, Jul 14, 2023 at 11:48:51AM -0600, Shuah Khan wrote:
> On 7/13/23 14:16, John Hubbard wrote:
> > Actually, I was hoping that my two fixes [1], [2] could be used, instead
> > of reverting the feature.
> Mark! Are you good with taking these two - do these fix the
> problems you are seeing?
I reviewed the one that's relevant to me already, the arm64 one, I'd not
seen or tested the RISC-V one but that looks fine too. I'm pretty sure
Andrew queued it already though ICBW. Either way it'd be good to get
this into -rc2, this is seriously disrupting arm64 CI and I'm guessing
the RISC-V CI too.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: John Hubbard <jhubbard@nvidia.com>, Shuah Khan <shuah@kernel.org>,
Andrew Morton <akpm@linux-foundation.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
Subject: Re: [PATCH] selftests: Fix arm64 test installation
Date: Fri, 14 Jul 2023 19:09:18 +0100 [thread overview]
Message-ID: <421bebb3-19e9-47a7-8b2b-f69f125df22f@sirena.org.uk> (raw)
In-Reply-To: <620a5b91-9715-ee28-423c-851506b10832@linuxfoundation.org>
[-- Attachment #1.1: Type: text/plain, Size: 604 bytes --]
On Fri, Jul 14, 2023 at 11:48:51AM -0600, Shuah Khan wrote:
> On 7/13/23 14:16, John Hubbard wrote:
> > Actually, I was hoping that my two fixes [1], [2] could be used, instead
> > of reverting the feature.
> Mark! Are you good with taking these two - do these fix the
> problems you are seeing?
I reviewed the one that's relevant to me already, the arm64 one, I'd not
seen or tested the RISC-V one but that looks fine too. I'm pretty sure
Andrew queued it already though ICBW. Either way it'd be good to get
this into -rc2, this is seriously disrupting arm64 CI and I'm guessing
the RISC-V CI too.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-07-14 18:09 UTC|newest]
Thread overview: 41+ 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 14:04 ` Mark Brown
2023-07-10 20:22 ` John Hubbard
2023-07-10 20:22 ` John Hubbard
2023-07-10 21:20 ` Mark Brown
2023-07-10 21:20 ` Mark Brown
2023-07-10 21:31 ` John Hubbard
2023-07-10 21:31 ` John Hubbard
2023-07-10 22:30 ` Mark Brown
2023-07-10 22:30 ` Mark Brown
2023-07-10 23:10 ` John Hubbard
2023-07-10 23:10 ` John Hubbard
2023-07-11 14:00 ` Mark Brown
2023-07-11 14:00 ` Mark Brown
2023-07-13 20:02 ` Shuah Khan
2023-07-13 20:02 ` Shuah Khan
2023-07-13 20:16 ` John Hubbard
2023-07-13 20:16 ` John Hubbard
2023-07-14 17:48 ` Shuah Khan
2023-07-14 17:48 ` Shuah Khan
2023-07-14 18:09 ` Mark Brown [this message]
2023-07-14 18:09 ` Mark Brown
2023-07-14 18:19 ` John Hubbard
2023-07-14 18:19 ` John Hubbard
2023-07-14 18:26 ` Andrew Morton
2023-07-14 18:26 ` Andrew Morton
2023-07-14 18:32 ` Shuah Khan
2023-07-14 18:32 ` Shuah Khan
2023-07-14 18:36 ` John Hubbard
2023-07-14 18:36 ` John Hubbard
2023-07-14 19:11 ` Shuah Khan
2023-07-14 19:11 ` Shuah Khan
2023-07-14 19:39 ` John Hubbard
2023-07-14 19:39 ` John Hubbard
2023-07-14 19:39 ` John Hubbard
2023-07-18 14:54 ` Mark Brown
2023-07-18 14:54 ` Mark Brown
2023-07-18 14:56 ` Shuah Khan
2023-07-18 14:56 ` Shuah Khan
2023-07-18 14:57 ` Mark Brown
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=421bebb3-19e9-47a7-8b2b-f69f125df22f@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=jhubbard@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.