From: Andrew Morton <akpm@linux-foundation.org>
To: Hongfu Li <lihongfu@kylinos.cn>
Cc: david@kernel.org, ljs@kernel.org, liam@infradead.org,
vbabka@kernel.org, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, shuah@kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] selftests/mm: refactor pkey helpers and fix mmap error handling
Date: Mon, 25 May 2026 13:02:00 -0700 [thread overview]
Message-ID: <20260525130200.fa26a0456979d8f1045dc930@linux-foundation.org> (raw)
In-Reply-To: <20260525073026.27594-1-lihongfu@kylinos.cn>
On Mon, 25 May 2026 15:30:24 +0800 Hongfu Li <lihongfu@kylinos.cn> wrote:
> This series is version 2 of the previous patch [0]. In v2, the changes are
> split into two patches for easier review.
> [0] https://lore.kernel.org/all/20260518082120.3890552-1-lihongfu@kylinos.cn/
>
> The main changes in this series are to refactor shared tracing and assertion
> helpers into a common file, unify both pkey selftests on pkey_assert() and
> per-test tracing for consistent diagnostics, and add missing mmap() return
> checks with MAP_FAILED used throughout for readability and consistency.
Thanks. AI review seems to have found a legitimate problem:
https://sashiko.dev/#/patchset/20260525073026.27594-1-lihongfu@kylinos.cn
next prev parent reply other threads:[~2026-05-25 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 7:30 Hongfu Li
2026-05-25 7:30 ` [PATCH v2 1/2] selftests/mm: refactor pkey test helpers and unify assertions Hongfu Li
2026-05-25 7:30 ` [PATCH v2 2/2] selftests/mm: add missing mmap() return checks in pkey tests Hongfu Li
2026-05-25 20:02 ` Andrew Morton [this message]
2026-05-26 7:05 ` [PATCH v2 0/2] selftests/mm: refactor pkey helpers and fix mmap error handling Hongfu Li
2026-05-27 16:24 ` Lorenzo Stoakes
2026-05-28 8:29 ` Hongfu Li
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=20260525130200.fa26a0456979d8f1045dc930@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--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=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--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
all inboxes | Powered by JetHome®