From: David Hildenbrand <david@redhat.com>
To: Florent Revest <revest@chromium.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: akpm@linux-foundation.org, catalin.marinas@arm.com,
anshuman.khandual@arm.com, joey.gouly@arm.com, mhocko@suse.com,
keescook@chromium.org, peterx@redhat.com, izbyshev@ispras.ru,
broonie@kernel.org, szabolcs.nagy@arm.com, kpsingh@kernel.org,
gthelen@google.com, toiwoton@gmail.com
Subject: Re: [PATCH v2 1/5] kselftest: vm: Fix tabs/spaces inconsistency in the mdwe test
Date: Mon, 22 May 2023 10:52:28 +0200 [thread overview]
Message-ID: <695a9b93-0dd5-d4c2-90a9-e33675d855ce@redhat.com> (raw)
In-Reply-To: <20230517150321.2890206-2-revest@chromium.org>
On 17.05.23 17:03, Florent Revest wrote:
> Signed-off-by: Florent Revest <revest@chromium.org>
> ---
> tools/testing/selftests/mm/mdwe_test.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/testing/selftests/mm/mdwe_test.c b/tools/testing/selftests/mm/mdwe_test.c
> index bc91bef5d254..d0954c657feb 100644
> --- a/tools/testing/selftests/mm/mdwe_test.c
> +++ b/tools/testing/selftests/mm/mdwe_test.c
> @@ -49,19 +49,19 @@ FIXTURE_VARIANT(mdwe)
>
> FIXTURE_VARIANT_ADD(mdwe, stock)
> {
> - .enabled = false,
> + .enabled = false,
> .forked = false,
> };
>
> FIXTURE_VARIANT_ADD(mdwe, enabled)
> {
> - .enabled = true,
> + .enabled = true,
> .forked = false,
> };
>
> FIXTURE_VARIANT_ADD(mdwe, forked)
> {
> - .enabled = true,
> + .enabled = true,
> .forked = true,
> };
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-05-22 8:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 15:03 [PATCH v2 0/5] MDWE without inheritance Florent Revest
2023-05-17 15:03 ` [PATCH v2 1/5] kselftest: vm: Fix tabs/spaces inconsistency in the mdwe test Florent Revest
2023-05-22 8:52 ` David Hildenbrand [this message]
2023-05-17 15:03 ` [PATCH v2 2/5] kselftest: vm: Fix mdwe's mmap_FIXED test case Florent Revest
2023-05-22 8:53 ` David Hildenbrand
2023-05-17 15:03 ` [PATCH v2 3/5] mm: Make PR_MDWE_REFUSE_EXEC_GAIN an unsigned long Florent Revest
2023-05-22 8:55 ` David Hildenbrand
[not found] ` <884d131bbc28ebfa0b729176e6415269@ispras.ru>
2023-05-22 16:22 ` David Hildenbrand
[not found] ` <3c2e210b75bd56909322e8a3e5086d91@ispras.ru>
2023-05-23 9:12 ` David Hildenbrand
2023-05-23 13:07 ` Catalin Marinas
[not found] ` <f47d587fe5a6285f88191fbb13f367c7@ispras.ru>
2023-05-23 14:09 ` Catalin Marinas
2023-05-23 15:01 ` Szabolcs Nagy
[not found] ` <7c572622c0d8e283fc880fe3f4ffac27@ispras.ru>
2023-05-23 14:10 ` David Hildenbrand
2023-05-26 19:04 ` Florent Revest
2023-05-26 19:02 ` Florent Revest
2023-05-23 14:11 ` Catalin Marinas
2023-05-17 15:03 ` [PATCH v2 4/5] mm: Add a NO_INHERIT flag to the PR_SET_MDWE prctl Florent Revest
2023-05-22 9:01 ` David Hildenbrand
2023-05-22 16:11 ` Florent Revest
2023-05-23 16:36 ` Catalin Marinas
2023-05-26 19:05 ` Florent Revest
2023-05-17 15:03 ` [PATCH v2 5/5] kselftest: vm: Add tests for no-inherit memory-deny-write-execute Florent Revest
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=695a9b93-0dd5-d4c2-90a9-e33675d855ce@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gthelen@google.com \
--cc=izbyshev@ispras.ru \
--cc=joey.gouly@arm.com \
--cc=keescook@chromium.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=peterx@redhat.com \
--cc=revest@chromium.org \
--cc=szabolcs.nagy@arm.com \
--cc=toiwoton@gmail.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