From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Li Wang <wangli.ahau@gmail.com>,
akpm@linux-foundation.org, ljs@kernel.org,
Liam.Howlett@oracle.com, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, shuah@kernel.org
Cc: linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] selftests/mm: clean up build output and verbosity
Date: Thu, 23 Apr 2026 15:31:14 +0200 [thread overview]
Message-ID: <7a762959-014c-4727-999f-a5073f9eaf7a@kernel.org> (raw)
In-Reply-To: <20260422080446.26020-1-wangli.ahau@gmail.com>
On 4/22/26 10:04, Li Wang wrote:
> Currently, the build process for the mm selftests is unnecessarily 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:
> My email address has changed due to employment change.
> Previous Signed-off-by was with <liwang@redhat.com>.
:(
As a former RH'er, I'm deeply sorry for what has happened there, really.
Thank you for continuing to contribute upstream, highly appreciated!
--
Cheers,
David
next prev parent reply other threads:[~2026-04-23 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 8:04 [PATCH v3 0/2] selftests/mm: clean up build output and verbosity Li Wang
2026-04-22 8:04 ` [PATCH v3 1/2] selftests/mm: respect build verbosity settings for 32/64-bit targets Li Wang
2026-04-23 13:38 ` David Hildenbrand (Arm)
2026-04-22 8:04 ` [PATCH v3 2/2] selftests/mm: suppress compiler error in liburing check Li Wang
2026-04-23 13:40 ` David Hildenbrand (Arm)
2026-04-23 13:31 ` David Hildenbrand (Arm) [this message]
2026-04-24 0:17 ` [PATCH v3 0/2] selftests/mm: clean up build output and verbosity Li Wang
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=7a762959-014c-4727-999f-a5073f9eaf7a@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=wangli.ahau@gmail.com \
/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