From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
wang lian <lianux.mm@gmail.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
Liam.Howlett@oracle.com, brauner@kernel.org,
gkwang@linx-info.com, jannh@google.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
p1ucky0923@gmail.com, ryncsn@gmail.com, shuah@kernel.org,
sj@kernel.org, vbabka@suse.cz, zijing.zhang@proton.me
Subject: Re: [PATCH] selftests/mm: Add process_madvise() tests
Date: Mon, 30 Jun 2025 16:02:13 +0200 [thread overview]
Message-ID: <30f2e2ed-00b9-4473-a0b7-29fb734fb3c4@redhat.com> (raw)
In-Reply-To: <694fca1d-1584-45d9-9e50-5c219b9c7c94@lucifer.local>
On 30.06.25 15:51, Lorenzo Stoakes wrote:
> On Sat, Jun 28, 2025 at 07:39:45PM +0800, wang lian wrote:
>> This patch adds tests for the process_madvise(), focusing on
>> verifying behavior under various conditions including valid
>> usage and error cases.
>
> Hi sorry to be a pain, but I'm not sure this will get picked up properly like this.
>
> Please resend this _not in reply to anything_ and with the subject:
>
> [PATCH v2] selftests/mm: add process_madvise() tests
>
Hehe, there is a
[PATCH v2] selftests/vm: Add process_madvise() tests
in my inbox, but looks like only you and me were on CC.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-06-30 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 14:36 [PATCH] selftests/mm: add test for (BATCH_PROCESS)MADV_DONTNEED wang lian
2025-06-23 14:39 ` Lorenzo Stoakes
2025-06-24 10:46 ` [PATCH] selftests: add basic test for MADV_POPULATE_(READ|WRITE) wang lian
2025-06-28 11:39 ` [PATCH] selftests/mm: Add process_madvise() tests wang lian
2025-06-30 13:51 ` Lorenzo Stoakes
2025-06-30 14:02 ` David Hildenbrand [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=30f2e2ed-00b9-4473-a0b7-29fb734fb3c4@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=gkwang@linx-info.com \
--cc=jannh@google.com \
--cc=lianux.mm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=p1ucky0923@gmail.com \
--cc=ryncsn@gmail.com \
--cc=shuah@kernel.org \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
--cc=zijing.zhang@proton.me \
/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