From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Park Tae-sun <ts930@dgu.ac.kr>
Cc: Sarthak Sharma <sarthak.sharma@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: mremap_test: handle ENOSYS for userfaultfd and add missing newlines
Date: Tue, 22 Sep 2026 09:06:14 +0100 [thread overview]
Message-ID: <arI2yv7TgtJLjMMr@gremlin> (raw)
In-Reply-To: <179006158019.123863.10328178989374348836@dgu.ac.kr>
On Tue, Sep 22, 2026 at 04:19:40PM +0900, Park Tae-sun wrote:
> Hi Sarthak,
>
> Thanks for letting me know!
>
> That sounds completely fine with me. I independently ran into the same
> issue while testing mremap_test in QEMU on a minimal kernel without
> CONFIG_USERFAULTFD, so I'm glad to see it addressed as part of your
> larger series.
>
> Feel free to add my:
> Tested-by: Park Tae-sun <ts930@dgu.ac.kr>
Additionally, for future reference - you were missing cc's.
Fixing this is easy with b4 [0] (the recommended way of sending patches to
mm):
$ b4 prep --auto-to-cc
Alternatively, you can use scripts/get_maintainer.pl:
$ scripts/get_maintainer.pl --nogit-fallback <files-or-patches>
[0]: https://b4.docs.kernel.org/en/latest/contributor/send.html
Specifically, the following appear to be missing:
david@kernel.org
liam@infradead.org
mhocko@suse.com
rppt@kernel.org
surenb@google.com
vbabka@kernel.org
>
> Thanks,
> Park Tae-sun
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-09-22 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 6:51 [PATCH] selftests/mm: mremap_test: handle ENOSYS for userfaultfd and add missing newlines Park Tae-sun
2026-09-22 7:09 ` Sarthak Sharma
2026-09-22 7:19 ` Park Tae-sun
2026-09-22 8:06 ` Lorenzo Stoakes (ARM) [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=arI2yv7TgtJLjMMr@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sarthak.sharma@arm.com \
--cc=shuah@kernel.org \
--cc=ts930@dgu.ac.kr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.