[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241203135941.GJ1245331@unreal>
Date: Tue, 3 Dec 2024 15:59:41 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH rdma-next] kbuild: Respect request to silent output when
merging configs
On Tue, Dec 03, 2024 at 03:55:18PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...dia.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@...dia.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
Powered by blists - more mailing lists