All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Shuah Khan <shuah@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/4] selftests/arm64: Fix O= builds for the FP selftests
Date: Thu, 28 Apr 2022 18:06:21 +0100	[thread overview]
Message-ID: <165116557542.4055682.1820773973319963164.b4-ty@arm.com> (raw)
In-Reply-To: <20220427181954.357975-1-broonie@kernel.org>

On Wed, 27 Apr 2022 19:19:50 +0100, Mark Brown wrote:
> Currently the arm64 selftests don't support building with O=, this
> series fixes that, bringing them more into line with how the kselftest
> Makefiles want to work.
> 
> v3:
>  - Rebase onto arm64/for-next/core.
> v2:
>  - Rebase onto v5.18-rc3.
> 
> [...]

Applied to arm64 (for-next/kselftest), thanks!

[1/4] selftests/arm64: Use TEST_GEN_PROGS_EXTENDED in the FP Makefile
      https://git.kernel.org/arm64/c/a59f7a7f7640
[2/4] selftests/arm64: Define top_srcdir for the fp tests
      https://git.kernel.org/arm64/c/3a23a42d1a48
[3/4] selftests/arm64: Clean the fp helper libraries
      https://git.kernel.org/arm64/c/399cf0a3e8a1
[4/4] selftests/arm64: Fix O= builds for the floating point tests
      https://git.kernel.org/arm64/c/aca43ad51661

-- 
Catalin


WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Shuah Khan <shuah@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/4] selftests/arm64: Fix O= builds for the FP selftests
Date: Thu, 28 Apr 2022 18:06:21 +0100	[thread overview]
Message-ID: <165116557542.4055682.1820773973319963164.b4-ty@arm.com> (raw)
In-Reply-To: <20220427181954.357975-1-broonie@kernel.org>

On Wed, 27 Apr 2022 19:19:50 +0100, Mark Brown wrote:
> Currently the arm64 selftests don't support building with O=, this
> series fixes that, bringing them more into line with how the kselftest
> Makefiles want to work.
> 
> v3:
>  - Rebase onto arm64/for-next/core.
> v2:
>  - Rebase onto v5.18-rc3.
> 
> [...]

Applied to arm64 (for-next/kselftest), thanks!

[1/4] selftests/arm64: Use TEST_GEN_PROGS_EXTENDED in the FP Makefile
      https://git.kernel.org/arm64/c/a59f7a7f7640
[2/4] selftests/arm64: Define top_srcdir for the fp tests
      https://git.kernel.org/arm64/c/3a23a42d1a48
[3/4] selftests/arm64: Clean the fp helper libraries
      https://git.kernel.org/arm64/c/399cf0a3e8a1
[4/4] selftests/arm64: Fix O= builds for the floating point tests
      https://git.kernel.org/arm64/c/aca43ad51661

-- 
Catalin


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-04-28 17:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 18:19 [PATCH v3 0/4] selftests/arm64: Fix O= builds for the FP selftests Mark Brown
2022-04-27 18:19 ` Mark Brown
2022-04-27 18:19 ` [PATCH v3 1/4] selftests/arm64: Use TEST_GEN_PROGS_EXTENDED in the FP Makefile Mark Brown
2022-04-27 18:19   ` Mark Brown
2022-04-27 18:19 ` [PATCH v3 2/4] selftests/arm64: Define top_srcdir for the fp tests Mark Brown
2022-04-27 18:19   ` Mark Brown
2022-04-27 18:19 ` [PATCH v3 3/4] selftests/arm64: Clean the fp helper libraries Mark Brown
2022-04-27 18:19   ` Mark Brown
2022-04-27 18:19 ` [PATCH v3 4/4] selftests/arm64: Fix O= builds for the floating point tests Mark Brown
2022-04-27 18:19   ` Mark Brown
2022-04-28 17:06 ` Catalin Marinas [this message]
2022-04-28 17:06   ` [PATCH v3 0/4] selftests/arm64: Fix O= builds for the FP selftests Catalin Marinas

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=165116557542.4055682.1820773973319963164.b4-ty@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=will@kernel.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 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.