From: Andrew Morton <akpm@linux-foundation.org>
To: Chunyu Hu <chuhu@redhat.com>
Cc: david@kernel.org, shuah@kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
vbabka@suse.cz, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, Luiz Capitulino <luizcap@redhat.com>
Subject: Re: [PATCH v2 1/5] selftests/mm: fix va_high_addr_switch.sh return value
Date: Sun, 21 Dec 2025 10:57:09 -0800 [thread overview]
Message-ID: <20251221105709.d2e44cf1bb05bd9669e76d0c@linux-foundation.org> (raw)
In-Reply-To: <20251221040025.3159990-1-chuhu@redhat.com>
On Sun, 21 Dec 2025 12:00:21 +0800 Chunyu Hu <chuhu@redhat.com> wrote:
> Patch series "Fix va_high_addr_switch.sh test failure - again", v2.
>
> The series address several issues exist for the va_high_addr_switch test:
> 1) the test return value is ignored in va_high_addr_switch.sh.
> 2) the va_high_addr_switch test requires 6 hugepages not 5.
> 3) the reurn value of the first test in va_high_addr_switch.c can be
> overridden by the second test.
> 4) the nr_hugepages setup in run_vmtests.sh for arm64 can be done in
> va_high_addr_switch.sh too.
> 5) update a comment for check_test_requirements.
>
> Changes in v2:
> - shorten the comment in for hugepages setup in v1
> - add a new patch to fix the return value overridden issue in
> va_high_addr_switch.c
> - fix a code comment for check_test_requirements.
> - update the series summary in patch 1
> - add reviewed-by from Luiz Capitulino on patch 1 and patch 3
The "Changes in v2" material is best placed below the "---" separator -
I prefer not to capture such short-term development-time info within
the permanent kernel record.
> This patch: (of 5)
>
> The return value should be return value of va_high_addr_switch, otherwise
> a test failure would be silently ignored.
>
> Reviewed-by: Luiz Capitulino <luizcap@redhat.com>
> Fixes: d9d957bd7b61 ("selftests/mm: alloc hugepages in va_high_addr_switch test")
> CC: Luiz Capitulino <luizcap@redhat.com>
> Signed-off-by: Chunyu Hu <chuhu@redhat.com>
>
> ...
>
> According to the doc below, I don't add the cover letter, not sure if cover
> letter is preferred, and if that's the case, the doc need an update.
Funnily enough, your series was in the exact format which I use when
committing patch series. Usually people put the cover letter in a
separate [0/N] email and I move that into the [1/N] patch's changelog,
as you've done here.
> https://www.ozlabs.org/~akpm/stuff/tpp.txt
God does that still exist? Pretty soon it will be able to legally
drink in bars.
I think its content got absorbed into a Documentation/ file a long time
ago!
next prev parent reply other threads:[~2025-12-21 18:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 4:00 Chunyu Hu
2025-12-21 4:00 ` [PATCH v2 2/5] selftests/mm: allocate 6 hugepages in va_high_addr_switch.sh Chunyu Hu
2025-12-21 4:00 ` [PATCH v2 3/5] selftests/mm: remove arm64 nr_hugepages setup for va_high_addr_switch test Chunyu Hu
2025-12-21 4:00 ` [PATCH v2 4/5] selftests/mm: va_high_addr_switch return fail when either test failed Chunyu Hu
2025-12-21 4:00 ` [PATCH v2 5/5] selftests/mm: fix comment for check_test_requirements Chunyu Hu
2025-12-22 19:37 ` Luiz Capitulino
2025-12-22 19:36 ` [PATCH v2 4/5] selftests/mm: va_high_addr_switch return fail when either test failed Luiz Capitulino
2025-12-23 2:46 ` Chunyu Hu
2025-12-23 2:56 ` Andrew Morton
2025-12-23 3:04 ` Chunyu Hu
2025-12-22 19:34 ` [PATCH v2 2/5] selftests/mm: allocate 6 hugepages in va_high_addr_switch.sh Luiz Capitulino
2025-12-21 18:57 ` Andrew Morton [this message]
2025-12-22 4:32 ` [PATCH v2 1/5] selftests/mm: fix va_high_addr_switch.sh return value Chunyu Hu
2025-12-23 1:15 ` SeongJae Park
2025-12-23 2:54 ` Chunyu Hu
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=20251221105709.d2e44cf1bb05bd9669e76d0c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=chuhu@redhat.com \
--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=luizcap@redhat.com \
--cc=mhocko@suse.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