From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
Tomasz Figa <tfiga@chromium.org>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] kconfig: add warn-unknown-symbols sanity check
Date: Sun, 3 Sep 2023 20:15:35 +0900 [thread overview]
Message-ID: <20230903111535.GH3913@google.com> (raw)
In-Reply-To: <CAK7LNAQvFR0dQAFU2YiqxrXJTKcH0-=n0Fea1Q8pc7ZuHHf0zg@mail.gmail.com>
On (23/08/31 23:56), Masahiro Yamada wrote:
> On Thu, Aug 31, 2023 at 11:15 PM Sergey Senozhatsky
> <senozhatsky@chromium.org> wrote:
> >
> > Introduce KCONFIG_WARN_UNKNOWN_SYMBOLS environment variable,
> > which makes Kconfig warn about unknown config symbols.
> >
> > This is especially useful for continuous kernel uprevs when
> > some symbols can be either removed or renamed between kernel
> > releases (which can go unnoticed otherwise).
> >
> > By default KCONFIG_WARN_UNKNOWN_SYMBOLS generates warnings,
> > which are non-terminal. There is an additional environment
> > variable KCONFIG_WERROR that overrides this behaviour and
> > turns warnings into errors.
> >
> > Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
>
>
> Applied to linux-kbuild. Thanks.
Thanks.
prev parent reply other threads:[~2023-09-03 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 0:49 [PATCHv2] kconfig: add warn-unknown-symbols sanity check Sergey Senozhatsky
2023-08-31 14:56 ` Masahiro Yamada
2023-09-03 11:15 ` Sergey Senozhatsky [this message]
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=20230903111535.GH3913@google.com \
--to=senozhatsky@chromium.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=tfiga@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).