From: "Zi Yan" <ziy@nvidia.com>
To: "Hongfu Li" <hongfu.li@linux.dev>, <akpm@linux-foundation.org>,
<david@kernel.org>, <ljs@kernel.org>,
<baolin.wang@linux.alibaba.com>, <liam@infradead.org>,
<nico.pache@linux.dev>, <ryan.roberts@arm.com>,
<dev.jain@arm.com>, <baohua@kernel.org>, <lance.yang@linux.dev>,
<usama.arif@linux.dev>, <vbabka@kernel.org>, <rppt@kernel.org>,
<surenb@google.com>, <mhocko@suse.com>, <shuah@kernel.org>
Cc: <linux-mm@kvack.org>, <linux-kselftest@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, "Hongfu Li" <lihongfu@kylinos.cn>
Subject: Re: [PATCH] selftests/mm: khugepaged: consolidate error exits via kselftest helpers
Date: Mon, 17 Aug 2026 22:10:37 -0400 [thread overview]
Message-ID: <DKRPDOBRL22H.3B54F0Q6F1AEX@nvidia.com> (raw)
In-Reply-To: <20260817061955.45454-1-hongfu.li@linux.dev>
On Mon Aug 17, 2026 at 2:19 AM EDT, Hongfu Li wrote:
> From: Hongfu Li <lihongfu@kylinos.cn>
>
> Replace the perror()+exit(EXIT_FAILURE) pattern with
> ksft_exit_fail_perror() so failures are reported through the
> kselftest framework, consistent with the rest of the file.
>
> Signed-off-by: Hongfu Li <lihongfu@kylinos.cn>
> ---
> tools/testing/selftests/mm/khugepaged.c | 20 +++++++-------------
> 1 file changed, 7 insertions(+), 13 deletions(-)
>
Thanks.
Reviewed-by: Zi Yan <ziy@nvidia.com>
--
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2026-08-18 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 6:19 [PATCH] selftests/mm: khugepaged: consolidate error exits via kselftest helpers Hongfu Li
2026-08-17 9:35 ` David Hildenbrand (Arm)
2026-08-17 11:19 ` Mike Rapoport
2026-08-18 2:10 ` Zi Yan [this message]
2026-08-18 5:38 ` Lance Yang
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=DKRPDOBRL22H.3B54F0Q6F1AEX@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hongfu.li@linux.dev \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=lihongfu@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=nico.pache@linux.dev \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@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