[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230826021054.GE3913@google.com>
Date: Sat, 26 Aug 2023 11:10:54 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Tomasz Figa <tfiga@...omium.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Ying Sun <sunying@...iscas.ac.cn>,
Jesse T <mr.bossman075@...il.com>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nicolas Schier <nicolas@...sle.eu>,
Jonathan Corbet <corbet@....net>, linux-kbuild@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] kconfig: introduce listunknownconfig
On (23/08/26 10:10), Masahiro Yamada wrote:
>
> I am considering how to implement it.
>
> One way is to add env variables as a new request arises.
>
> Sergey is doing two things by one option.
>
> KCONFIG_WARN_UNKNWON_SYMBOL : warn unknown symbol in input .config
> or defconfig
> KCONFIG_WARN_TO_ERROR : turn warnings into errors
>
> Another way is to handle those as command line options.
>
> -Wunknown-symbol
> -Werror (associated with W=e)
> -Wall (associated with W=1)
>
> $ make W=1e olddefconfig
>
> will work to sanity check.
Sounds good. Being able to choose whether those sanity checks are
warnings or errors is quite handful.
I don't have preferences as to implementation. Env variables seem to
have very clear and descriptive names. Command line options look fine
too. I'd probably prefer command line args.
Powered by blists - more mailing lists