From: Nathan Chancellor <nathan@kernel.org>
To: Li Wang <liwang@redhat.com>
Cc: nsc@kernel.org, akpm@linux-foundation.org, david@kernel.org,
ljs@kernel.org, Liam.Howlett@oracle.com, 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,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 0/2] selftests/mm: clean up build output and verbosity
Date: Mon, 6 Apr 2026 12:32:16 -0700 [thread overview]
Message-ID: <20260406193216.GA1319599@ax162> (raw)
In-Reply-To: <20260331094402.144131-1-liwang@redhat.com>
On Tue, Mar 31, 2026 at 05:44:00PM +0800, Li Wang wrote:
> Currently, the mm selftests build process can be quite noisy.
>
> First, it leaks raw compiler errors during the liburing feature probe if
> the headers are missing, which is confusing since the build system already
> handles this gracefully with a clear warning.
>
> Second, the specific 32-bit and 64-bit compilation targets ignore the
> standard kbuild verbosity settings, always printing their full compiler
> commands even during a default quiet build.
>
> Notes:
> Andrew mentioned he hopes this patch merge into kbuild tree, so I resend
> to linux-kbuild@vger.kernel.org.
Kbuild does not maintain anything in tools/, so this should go through
either the mm tree or the kselftests tree.
> V2:
>
> - Drop 2/4, 3/4 from v1 to v2, since Andrew wasn't able to confirm the
> patch works for the rarely happening issue now, so I decided to just
> hand on the process of the parallel issue.
>
> - Refine the 4/4 patch only to hide compiler errors when missing liburing.
>
> Li Wang (2):
> selftests/mm: respect build verbosity settings for 32/64-bit targets
> selftests/mm: suppress compiler error in liburing check
>
> tools/testing/selftests/mm/Makefile | 9 ++++++---
> tools/testing/selftests/mm/check_config.sh | 2 +-
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-04-06 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 9:44 [PATCH v2 0/2] selftests/mm: clean up build output and verbosity Li Wang
2026-03-31 9:44 ` [PATCH v2 1/2] selftests/mm: respect build verbosity settings for 32/64-bit targets Li Wang
2026-03-31 9:44 ` [PATCH v2 2/2] selftests/mm: suppress compiler error in liburing check Li Wang
2026-04-06 19:32 ` Nathan Chancellor [this message]
2026-04-06 19:51 ` [PATCH v2 0/2] selftests/mm: clean up build output and verbosity Andrew Morton
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=20260406193216.GA1319599@ax162 \
--to=nathan@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwang@redhat.com \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=nsc@kernel.org \
--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