From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
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: [RFC][PATCH] kconfig: introduce listunknownconfig
Date: Thu, 17 Aug 2023 12:44:43 +0900 [thread overview]
Message-ID: <20230817034443.GF681074@google.com> (raw)
In-Reply-To: <20230817012007.131868-1-senozhatsky@chromium.org>
On (23/08/17 10:19), Sergey Senozhatsky wrote:
> The listunknownconfig option reads old .config and lists
> all unrecognized 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).
>
> A recent real-life example of such a symbol rename
> that quietly disabled some drivers after kernel uprev
> is MFD_RK808 rename.
>
> Example:
> Suppose old .config has the following two options which
> were removed from the recent kernel:
>
> $ cat .config
> CONFIG_DISABLE_BUGS=y
Uh, I see what happened there. The correct output is
$ cat .config
CONFIG_DISABLE_BUGS=y
# CONFIG_ENABLE_WINAPI is not set
next prev parent reply other threads:[~2023-08-17 3:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 1:19 [RFC][PATCH] kconfig: introduce listunknownconfig Sergey Senozhatsky
2023-08-17 3:44 ` Sergey Senozhatsky [this message]
2023-08-19 23:19 ` Masahiro Yamada
2023-08-20 2:45 ` Sergey Senozhatsky
2023-08-20 4:58 ` Sergey Senozhatsky
2023-08-20 5:11 ` Masahiro Yamada
2023-08-20 7:21 ` Sergey Senozhatsky
2023-08-20 7:33 ` Sergey Senozhatsky
2023-08-21 12:27 ` Masahiro Yamada
2023-08-21 16:08 ` Sergey Senozhatsky
2023-08-22 6:12 ` Sergey Senozhatsky
2023-08-24 1:00 ` Masahiro Yamada
2023-08-24 1:20 ` Sergey Senozhatsky
2023-08-26 1:12 ` Masahiro Yamada
2023-08-26 5:38 ` Masahiro Yamada
2023-08-26 5:53 ` Sergey Senozhatsky
2023-08-24 1:51 ` Tomasz Figa
2023-08-26 1:10 ` Masahiro Yamada
2023-08-26 2:10 ` Sergey Senozhatsky
2023-08-30 7:30 ` Tomasz Figa
2023-08-31 15:28 ` Masahiro Yamada
2023-09-04 5:10 ` Tomasz Figa
2023-12-28 5:51 ` Tomasz Figa
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=20230817034443.GF681074@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=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--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).