From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Tomasz Figa <tfiga@chromium.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: kconfig: list unknown symbols in the old .config
Date: Wed, 16 Aug 2023 21:42:21 +0900 [thread overview]
Message-ID: <20230816124221.GH907732@google.com> (raw)
Hi,
We recently were hit (unnecessarily hard) when after kernel uprev we
figured that something wasn't working. The root cause was a rename of
the CONFIG_FOO option between kernel releases, which make oldconfig
doesn't warn/notify about.
Would it be possible to add either a new --listunknown mode to conf or
to somehow make it conf_warning("unknown symbol: %s\n", line) when it
reads a line from oldconf that it cannot sym_find()?
That would save a ton of time.
next reply other threads:[~2023-08-16 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 12:42 Sergey Senozhatsky [this message]
2023-08-16 13:06 ` kconfig: list unknown symbols in the old .config Sergey Senozhatsky
2023-08-19 19:54 ` Jesse T
2023-08-20 2:30 ` Sergey Senozhatsky
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=20230816124221.GH907732@google.com \
--to=senozhatsky@chromium.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