Re: [PATCH 1/1] kconfig: warn if an unknown symbol is selected

2015-01-29 Thread Michal Marek
On 2015-01-28 22:32, Paul Bolle wrote: > On Wed, 2015-01-28 at 16:26 +0100, Michal Marek wrote: >> On 2015-01-28 10:54, Paul Bolle wrote: >>> Now that we've been told Yann has disappeared, would you consider taking >>> this patch into one of your trees? It would be nice to have people >>> actually

Re: [PATCH 1/1] kconfig: warn if an unknown symbol is selected

2015-01-28 Thread Michal Marek
On 2015-01-28 10:54, Paul Bolle wrote: > Now that we've been told Yann has disappeared, would you consider taking > this patch into one of your trees? It would be nice to have people > actually use it for a while. > > Or should we first clean up (most of) the warnings it generates? There It seems

Re: [PATCH 1/1] kconfig: warn if an unknown symbol is selected

2015-01-28 Thread Paul Bolle
On Wed, 2015-01-28 at 16:26 +0100, Michal Marek wrote: > On 2015-01-28 10:54, Paul Bolle wrote: > > Now that we've been told Yann has disappeared, would you consider taking > > this patch into one of your trees? It would be nice to have people > > actually use it for a while. > > > > Or should we

Re: [PATCH 1/1] kconfig: warn if an unknown symbol is selected

2014-11-03 Thread Paul Bolle
Hi Yann, On Tue, 2014-09-30 at 20:09 +0200, Paul Bolle wrote: > A select of an unknown symbol is basically treated as a nop and is > silently skipped. This is annoying if the selected symbol contains a > typo. It can also hide the fact that a treewide symbol cleanup was only > done partially. > >

[PATCH 1/1] kconfig: warn if an unknown symbol is selected

2014-09-30 Thread Paul Bolle
A select of an unknown symbol is basically treated as a nop and is silently skipped. This is annoying if the selected symbol contains a typo. It can also hide the fact that a treewide symbol cleanup was only done partially. There are also a few cases were this might have been done on purpose. But