Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Mark Brown <broonie@kernel.org>,
	Shuah Khan <skhan@linuxfoundation.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 11:26:53 -0700	[thread overview]
Message-ID: <20230714112653.0b42d3c9818b038d219b5e41@linux-foundation.org> (raw)
In-Reply-To: <f479b731-7782-0417-2d4c-31a7c3c9491c@nvidia.com>

On Fri, 14 Jul 2023 11:19:11 -0700 John Hubbard <jhubbard@nvidia.com> wrote:

> On 7/14/23 11:09, Mark Brown wrote:
> > 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
> 
> That riscv patch already has a Tested-by from Alexandre Ghiti:
> 
> https://lore.kernel.org/f903634d-851f-af64-8d9a-6b13d813587c@ghiti.fr
> 
> 
> > 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.
> 

I just dropped
selftests-arm64-fix-build-failure-during-the-emit_tests-step.patch and
selftests-fix-arm64-test-installation.patch, as Shuah is merging them.

This is all rather confusing.  Perhaps a full resend of everything will
help.  I'll assume that Shuah will be handling them.

  reply	other threads:[~2023-07-14 18:26 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 [this message]
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
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=20230714112653.0b42d3c9818b038d219b5e41@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=anders.roxell@linaro.org \
    --cc=broonie@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox