From: David Hildenbrand <david@redhat.com>
To: Mark Brown <broonie@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>
Cc: linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] selftests/mm: Use standard ksft_finished() in cow and gup_longterm
Date: Tue, 27 May 2025 14:34:00 +0200 [thread overview]
Message-ID: <0f09b648-bf0e-4b7a-99ef-a7a42cb20054@redhat.com> (raw)
In-Reply-To: <20250522-selftests-mm-cow-dedupe-v1-1-713cee2fdd6d@kernel.org>
On 22.05.25 19:38, Mark Brown wrote:
> The cow and gup_longterm test programs open code something that looks a
> lot like the standard ksft_finished() helper to summarise the test
> results and provide an exit code, convert to use ksft_finished().
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-05-27 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 17:38 [PATCH 0/4] selftests/mm: cow and gup_longterm cleanups Mark Brown
2025-05-22 17:38 ` [PATCH 1/4] selftests/mm: Use standard ksft_finished() in cow and gup_longterm Mark Brown
2025-05-27 12:34 ` David Hildenbrand [this message]
2025-05-22 17:38 ` [PATCH 2/4] selftest/mm: Add helper for logging test start and results Mark Brown
2025-05-22 17:38 ` [PATCH 3/4] selftests/mm: Report unique test names for each cow test Mark Brown
2025-05-27 10:08 ` Lorenzo Stoakes
2025-05-27 11:49 ` Mark Brown
2025-05-27 11:53 ` Lorenzo Stoakes
2025-05-27 12:06 ` Mark Brown
2025-05-27 13:06 ` Mark Brown
2025-05-22 17:38 ` [PATCH 4/4] selftests/mm: Fix test result reporting in gup_longterm Mark Brown
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=0f09b648-bf0e-4b7a-99ef-a7a42cb20054@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@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