On (23/08/19 15:54), Jesse T wrote:
> > 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.
I posted an RFC patch a couple of days ago
https://lore.kernel.org/all/20230817012007.131868-1-senozhatsky@xxxxxxxxxxxx/T/#u
