From: Miaohe Lin <linmiaohe@huawei.com>
To: Mark Brown <broonie@kernel.org>
Cc: <akpm@linux-foundation.org>, <shuah@kernel.org>,
<david@kernel.org>, <lorenzo.stoakes@oracle.com>,
<Liam.Howlett@oracle.com>, <vbabka@suse.cz>, <rppt@kernel.org>,
<surenb@google.com>, <mhocko@suse.com>, <nao.horiguchi@gmail.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] selftests/mm: add memory failure anonymous page test
Date: Fri, 6 Feb 2026 10:36:06 +0800 [thread overview]
Message-ID: <92c543fd-4316-d5dd-451a-a2c668fc98aa@huawei.com> (raw)
In-Reply-To: <73756615-b779-44b1-8ff5-b4b2d5e3c7cf@sirena.org.uk>
On 2026/2/5 19:28, Mark Brown wrote:
> On Thu, Feb 05, 2026 at 02:58:50PM +0800, Miaohe Lin wrote:
>> On 2026/2/4 19:26, Mark Brown wrote:
>
>>> In -next I added a hack with wrapper scripts per category to improve the
>>> integration of the mm selftests with the kselftest framework, could you
>>> please wire things up into that, see:
>
>> Sorry, I missed that. Do you mean adding something like below to run memory-failure test separately?
>
> Yes, pretty much - I'd keep the list of TEST_PROGS sorted but otherwise
> that's it.
Sounds good to me. Will do.
Thanks.
.
next prev parent reply other threads:[~2026-02-06 2:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 7:33 [PATCH v3 0/3] selftests/mm: add memory failure selftests Miaohe Lin
2026-02-04 7:33 ` [PATCH v3 1/3] selftests/mm: add memory failure anonymous page test Miaohe Lin
2026-02-04 11:26 ` Mark Brown
2026-02-05 6:58 ` Miaohe Lin
2026-02-05 11:28 ` Mark Brown
2026-02-06 2:36 ` Miaohe Lin [this message]
2026-02-04 7:33 ` [PATCH v3 2/3] selftests/mm: add memory failure clean pagecache test Miaohe Lin
2026-02-04 7:33 ` [PATCH v3 3/3] selftests/mm: add memory failure dirty " Miaohe Lin
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=92c543fd-4316-d5dd-451a-a2c668fc98aa@huawei.com \
--to=linmiaohe@huawei.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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