From: Catalin Marinas <catalin.marinas@arm.com>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, nd@arm.com, broonie@kernel.org,
shuah@kernel.org, skhan@linuxfoundation.org, will@kernel.org
Subject: Re: [PATCH v3 2/6] kselftest/arm64: mte: user_mem: rework error handling
Date: Wed, 9 Feb 2022 18:40:01 +0000 [thread overview]
Message-ID: <YgQKgY7yfpVh9Opn@arm.com> (raw)
In-Reply-To: <20220209152240.52788-3-joey.gouly@arm.com>
On Wed, Feb 09, 2022 at 03:22:36PM +0000, Joey Gouly wrote:
> Future commits will have multiple iterations of tests in this function,
> so make the error handling assume it will pass and then bail out if there
> is an error.
>
> Signed-off-by: Joey Gouly <joey.gouly@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Shuah Khan <shuah@kernel.org>
> Reviewed-by: Mark Brown <broonie@kernel.org>
> Tested-by: Mark Brown <broonie@kernel.org>
> Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, nd@arm.com, broonie@kernel.org,
shuah@kernel.org, skhan@linuxfoundation.org, will@kernel.org
Subject: Re: [PATCH v3 2/6] kselftest/arm64: mte: user_mem: rework error handling
Date: Wed, 9 Feb 2022 18:40:01 +0000 [thread overview]
Message-ID: <YgQKgY7yfpVh9Opn@arm.com> (raw)
In-Reply-To: <20220209152240.52788-3-joey.gouly@arm.com>
On Wed, Feb 09, 2022 at 03:22:36PM +0000, Joey Gouly wrote:
> Future commits will have multiple iterations of tests in this function,
> so make the error handling assume it will pass and then bail out if there
> is an error.
>
> Signed-off-by: Joey Gouly <joey.gouly@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Shuah Khan <shuah@kernel.org>
> Reviewed-by: Mark Brown <broonie@kernel.org>
> Tested-by: Mark Brown <broonie@kernel.org>
> Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
_______________________________________________
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:[~2022-02-09 18:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 15:22 [PATCH v3 0/6] add more test coverage to MTE kselftests Joey Gouly
2022-02-09 15:22 ` Joey Gouly
2022-02-09 15:22 ` [PATCH v3 1/6] kselftest/arm64: mte: user_mem: introduce tag_offset and tag_len Joey Gouly
2022-02-09 15:22 ` Joey Gouly
2022-02-09 18:36 ` Catalin Marinas
2022-02-09 18:36 ` Catalin Marinas
2022-02-09 15:22 ` [PATCH v3 2/6] kselftest/arm64: mte: user_mem: rework error handling Joey Gouly
2022-02-09 15:22 ` Joey Gouly
2022-02-09 18:40 ` Catalin Marinas [this message]
2022-02-09 18:40 ` Catalin Marinas
2022-02-09 15:22 ` [PATCH v3 3/6] kselftest/arm64: mte: user_mem: check different offsets and sizes Joey Gouly
2022-02-09 15:22 ` Joey Gouly
2022-02-09 18:41 ` Catalin Marinas
2022-02-09 18:41 ` Catalin Marinas
2022-02-09 15:22 ` [PATCH v3 4/6] kselftest/arm64: mte: user_mem: add test type enum Joey Gouly
2022-02-09 15:22 ` Joey Gouly
2022-02-09 18:43 ` Catalin Marinas
2022-02-09 18:43 ` Catalin Marinas
2022-02-09 15:22 ` [PATCH v3 5/6] kselftest/arm64: mte: user_mem: add more test types Joey Gouly
2022-02-09 15:22 ` Joey Gouly
2022-02-09 18:43 ` Catalin Marinas
2022-02-09 18:43 ` Catalin Marinas
2022-02-09 15:22 ` [PATCH v3 6/6] kselftest/arm64: mte: user_mem: test a wider range of values Joey Gouly
2022-02-09 15:22 ` Joey Gouly
2022-02-09 18:44 ` Catalin Marinas
2022-02-09 18:44 ` Catalin Marinas
2022-02-15 23:18 ` [PATCH v3 0/6] add more test coverage to MTE kselftests Will Deacon
2022-02-15 23:18 ` Will Deacon
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=YgQKgY7yfpVh9Opn@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--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=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.