public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Joey Gouly <joey.gouly@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kselftest@vger.kernel.org, nd@arm.com
Subject: Re: [PATCH v1 4/4] kselftest/arm64: Add simple test for MTE prctl
Date: Thu, 10 Mar 2022 15:37:15 +0000	[thread overview]
Message-ID: <YiobK0180DsCfza6@sirena.org.uk> (raw)
In-Reply-To: <20220310153306.GA53610@e124191.cambridge.arm.com>

[-- Attachment #1: Type: text/plain, Size: 267 bytes --]

On Thu, Mar 10, 2022 at 03:33:06PM +0000, Joey Gouly wrote:
> On Thu, Mar 10, 2022 at 02:43:35PM +0000, Mark Brown wrote:

> > +static bool system_has_mte;

> This looks unused (apart from being set in main()).

It is, it was used in the asymmetric bits of the test.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-03-10 15:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 14:43 [PATCH v1 0/4] kselftest/arm64: Miscelaneous MTE test updates Mark Brown
2022-03-10 14:43 ` [PATCH v1 1/4] kselftest/arm64: Handle more kselftest result codes in MTE helpers Mark Brown
2022-03-10 19:40   ` Shuah Khan
2022-03-10 14:43 ` [PATCH v1 2/4] kselftest/arm64: Log unexpected asynchronous MTE faults Mark Brown
2022-03-10 20:04   ` Shuah Khan
2022-03-10 14:43 ` [PATCH v1 3/4] kselftest/arm64: Refactor parameter checking in mte_switch_mode() Mark Brown
2022-03-10 20:05   ` Shuah Khan
2022-03-10 14:43 ` [PATCH v1 4/4] kselftest/arm64: Add simple test for MTE prctl Mark Brown
2022-03-10 15:33   ` Joey Gouly
2022-03-10 15:37     ` Mark Brown [this message]
2022-03-10 20:07   ` Shuah Khan

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=YiobK0180DsCfza6@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=nd@arm.com \
    --cc=shuah@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox