From: Leon Romanovsky <leon@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH rdma-next] kbuild: Respect request to silent output when merging configs
Date: Tue, 3 Dec 2024 15:59:41 +0200 [thread overview]
Message-ID: <20241203135941.GJ1245331@unreal> (raw)
In-Reply-To: <e534ce33b0e1060eb85ece8429810f087b034c88.1733234008.git.leonro@nvidia.com>
On Tue, Dec 03, 2024 at 03:55:18PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Builds with -s option (silent) are supposed to silence all output
> which is not an error. It is the case for target builds but not
> for configs. These builds generate prints like this:
>
> ➜ kernel git:(rdma-next) make -s defconfig debug.config
> Using .config as base
> Merging ./kernel/configs/debug.config
> #
> # merged configuration written to .config (needs make)
> #
> ...
> Value of CONFIG_FUNCTION_TRACER is redefined by fragment ./kernel/configs/debug.config:
> Previous value: # CONFIG_FUNCTION_TRACER is not set
> New value: CONFIG_FUNCTION_TRACER=y
> ----
>
> Let's honor -s option and hide all non-error output.
>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> ---
> scripts/kconfig/Makefile | 3 ++-
> scripts/kconfig/merge_config.sh | 18 +++++++++++++-----
> 2 files changed, 15 insertions(+), 6 deletions(-)
Masahiro,
I hope that you don't mind that I put "rdma-next" as a target. It wasn't
intentionally, and bug in my submission scripts.
Thanks
next prev parent reply other threads:[~2024-12-03 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 13:55 [PATCH rdma-next] kbuild: Respect request to silent output when merging configs Leon Romanovsky
2024-12-03 13:59 ` Leon Romanovsky [this message]
2024-12-04 8:25 ` Masahiro Yamada
2024-12-04 8:49 ` Leon Romanovsky
2024-12-08 14:49 ` Masahiro Yamada
2024-12-08 16:35 ` Leon Romanovsky
2024-12-09 5:34 ` Masahiro Yamada
2024-12-09 8:43 ` Leon Romanovsky
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=20241203135941.GJ1245331@unreal \
--to=leon@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.