[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 26 Aug 2023 10:12:05 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: 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>,
Tomasz Figa <tfiga@...omium.org>, linux-kbuild@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] kconfig: introduce listunknownconfig
On Thu, Aug 24, 2023 at 7:50 PM Sergey Senozhatsky
<senozhatsky@...omium.org> wrote:
>
> On (23/08/24 10:00), Masahiro Yamada wrote:
>
> > For the MFD_RK808 case particularly,
> > I believe Kconfig showed MFD_RK8XX_I2C
> > as a new option.
>
> I think there were some other unmet dependencies for MFD_RK8XX_I2C and
> I don't think the new config was shown. But even if it was, we still
> would have no idea that this meant "MFD_RK808 is not available anymore
> and the corresponding code won't get compiled". So the "this is not
> recognized anymore" is still needed and is quite helpful.
>
> Would you be OK with "list missing" being a warning (not a terminal
> condition)?
I am fine with implementing both.
But, I'd like to implement them as separate options.
(one option for warn unknown symbols,
another for for turning warnings into errors)
As I replied to Tomasz, I am considering about
env variables vs command line options associated with W= option.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists