Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Shuah Khan <shuah@kernel.org>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Amit Daniel Kachhap <amit.kachhap@arm.com>,
	Yeoreum Yun <yeoreum.yun@arm.com>,
	Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kselftest@vger.kernel.org,
	Muhammad Usama Anjum <usama.anjum@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH v3 0/4] selftests/arm64: Fix MTE test setup and TAP reporting
Date: Thu, 27 Aug 2026 16:22:38 +0100	[thread overview]
Message-ID: <178784032021.66644.7509441879156473484.b4-ty@kernel.org> (raw)
In-Reply-To: <20260825111929.2882324-1-usama.anjum@arm.com>

On Tue, 25 Aug 2026 12:18:33 +0100, Muhammad Usama Anjum wrote:
> Running the mainline arm64 MTE selftests on a Pixel 8 exposed three
> independent reporting problems. Fix these reporting problems, then add
> an arm64 Kconfig fragment covering the facilities used by the MTE tests.
> 
> Testing was performed on a Pixel 8 with an Android 6.1 kernel built with
> the new configuration. All nine static MTE binaries returned success.
> 
> [...]

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

[1/4] selftests/arm64: Print missing MTE TAP headers
      https://git.kernel.org/arm64/c/8d2237e9d690
[2/4] selftests/arm64: Treat KSM merge_across_nodes as optional
      https://git.kernel.org/arm64/c/1a0dba077f34
[3/4] selftests/arm64: Fix MTE prctl TAP plan
      https://git.kernel.org/arm64/c/bb52892f9234
[4/4] selftests/arm64: Add MTE test config fragment
      https://git.kernel.org/arm64/c/2bd533739234

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev


      parent reply	other threads:[~2026-08-27 15:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 11:18 [PATCH v3 0/4] selftests/arm64: Fix MTE test setup and TAP reporting Muhammad Usama Anjum
2026-08-25 11:18 ` [PATCH v3 1/4] selftests/arm64: Print missing MTE TAP headers Muhammad Usama Anjum
2026-08-25 13:58   ` Mark Brown
2026-08-26  8:25   ` Vincenzo Frascino
2026-08-25 11:18 ` [PATCH v3 2/4] selftests/arm64: Treat KSM merge_across_nodes as optional Muhammad Usama Anjum
2026-08-25 14:00   ` Mark Brown
2026-08-26  8:26   ` Vincenzo Frascino
2026-08-25 11:18 ` [PATCH v3 3/4] selftests/arm64: Fix MTE prctl TAP plan Muhammad Usama Anjum
2026-08-26  8:27   ` Vincenzo Frascino
2026-08-25 11:18 ` [PATCH v3 4/4] selftests/arm64: Add MTE test config fragment Muhammad Usama Anjum
2026-08-26  8:27   ` Vincenzo Frascino
2026-08-27 15:22 ` Will Deacon [this message]

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=178784032021.66644.7509441879156473484.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=amit.kachhap@arm.com \
    --cc=andreyknvl@gmail.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=shuah@kernel.org \
    --cc=usama.anjum@arm.com \
    --cc=vincenzo.frascino@arm.com \
    --cc=yeoreum.yun@arm.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