From: Li Wang <liwang@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
nsc@kernel.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: Tue, 7 Apr 2026 10:31:05 +0800 [thread overview]
Message-ID: <adRsadO77aF3WcWm@redhat.com> (raw)
In-Reply-To: <20260406125133.eeb8efed993ae1faa2a9ad73@linux-foundation.org>
On Mon, Apr 06, 2026 at 12:51:33PM -0700, Andrew Morton wrote:
> On Mon, 6 Apr 2026 12:32:16 -0700 Nathan Chancellor <nathan@kernel.org> wrote:
>
> > > 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.
>
> No probs. Li, please send it along after -rc1?
Sure thing!
--
Regards,
Li Wang
prev parent reply other threads:[~2026-04-07 2:31 UTC|newest]
Thread overview: 6+ 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 ` [PATCH v2 0/2] selftests/mm: clean up build output and verbosity Nathan Chancellor
2026-04-06 19:51 ` Andrew Morton
2026-04-07 2:31 ` Li Wang [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=adRsadO77aF3WcWm@redhat.com \
--to=liwang@redhat.com \
--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=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=nathan@kernel.org \
--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