[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJFTR8SW=csT9o6iFdaVn7L8P38xYwcf2oU0Qd762=kOtrcs7w@mail.gmail.com>
Date: Sat, 19 Aug 2023 15:54:12 -0400
From: Jesse T <mr.bossman075@...il.com>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>,
Tomasz Figa <tfiga@...omium.org>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>
Subject: Re: kconfig: list unknown symbols in the old .config
On Sat, Aug 19, 2023 at 3:37 PM Sergey Senozhatsky
<senozhatsky@...omium.org> wrote:
>
> 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()?
This makes sense and I brought up this scenario a couple of days ago
on a recent patch.
I can make a patch for this if needed.
Thanks,
Jesse Taube
>
> That would save a ton of time.
Powered by blists - more mailing lists