Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Pedro Falcato <pedro.falcato@gmail.com>
To: pedro.falcato@gmail.com, akpm@linux-foundation.org
Cc: Liam.Howlett@oracle.com, jeffxu@chromium.org, kees@kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-mm@kvack.org, shuah@kernel.org
Subject: [PATCH] fixup! selftests/mm: Add mseal test for no-discard madvise
Date: Wed,  7 Aug 2024 21:37:24 +0100	[thread overview]
Message-ID: <20240807203724.2686144-1-pedro.falcato@gmail.com> (raw)
In-Reply-To: <20240807173336.2523757-3-pedro.falcato@gmail.com>

Adjust the mseal test's plan.

Signed-off-by: Pedro Falcato <pedro.falcato@gmail.com>

---

Andrew, please squash this small fix into "selftests/mm: Add mseal test for no-discard madvise".
Thank you!

 tools/testing/selftests/mm/mseal_test.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/mm/mseal_test.c b/tools/testing/selftests/mm/mseal_test.c
index 2dcda7440eb..7eec3f0152e 100644
--- a/tools/testing/selftests/mm/mseal_test.c
+++ b/tools/testing/selftests/mm/mseal_test.c
@@ -1775,7 +1775,7 @@ int main(int argc, char **argv)
 	if (!pkey_supported())
 		ksft_print_msg("PKEY not supported\n");
 
-	ksft_set_plan(80);
+	ksft_set_plan(82);
 
 	test_seal_addseal();
 	test_seal_unmapped_start();
-- 
2.46.0


      reply	other threads:[~2024-08-07 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 17:33 [PATCH 0/2] mseal: Fix is_madv_discard() Pedro Falcato
2024-08-07 17:33 ` [PATCH 1/2] " Pedro Falcato
2024-08-07 18:58   ` Andrew Morton
2024-08-07 19:25     ` Pedro Falcato
2024-08-07 19:31       ` Andrew Morton
2024-08-07 17:33 ` [PATCH 2/2] selftests/mm: Add mseal test for no-discard madvise Pedro Falcato
2024-08-07 20:37   ` Pedro Falcato [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=20240807203724.2686144-1-pedro.falcato@gmail.com \
    --to=pedro.falcato@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeffxu@chromium.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shuah@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