[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAFQd5CRtgMUN8xZ_4BOv04KzCvXtrKHhWGQhhqgENyMCVWbKw@mail.gmail.com>
Date: Wed, 10 Jan 2024 22:14:55 +0900
From: Tomasz Figa <tfiga@...omium.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
Sergey Senozhatsky <senozhatsky@...omium.org>
Subject: Re: [PATCH] kconfig: Add a build target for checking current config
for issues
On Fri, Dec 29, 2023 at 1:11 AM Masahiro Yamada <masahiroy@...nel.org> wrote:
>
> On Thu, Dec 28, 2023 at 4:09 PM Tomasz Figa <tfiga@...omium.org> wrote:
> >
> > The new target is called 'checkconfig' and currently is basically an
> > alias for `listnewconfig` with KCONFIG_WARN_UNKNOWN_SYMBOLS set to true.
> > It can be used to validate if the current config is directly compatible
> > with the current kernel version or needs some manual adjustment.
> >
> > Signed-off-by: Tomasz Figa <tfiga@...omium.org>
>
>
> I rejected a new target in the past.
>
> https://lore.kernel.org/all/20230817012007.131868-1-senozhatsky@chromium.org/T/#m55c37e3091158f8cb008d9e0b5c6bf3f5ead225a
>
That was specifically for the unrecognized symbols warning. What I'm
proposing is a universal target that would include any possible
diagnostics.
>
>
> Instead, you can run
>
> KCONFIG_WARN_UNKNOWN_SYMBOLS=1 make listnewconfig
>
> or
>
> make W=c listnewconfig
>
>
I can do so, because my team member implemented it and told me and
other team members about it. But how would someone who hasn't heard
about it be aware of the existence of this useful feature?
Best regards,
Tomasz
Powered by blists - more mailing lists