Thanks for this clarification...
On Fri, Mar 11, 2016 at 10:18 AM, Tom Rini <tr...@konsulko.com> wrote: > On Fri, Mar 11, 2016 at 10:07:46AM -0800, Steve Rae wrote: > >> Is it expected the _every_ CONFIG_* and CONFIG_SYS_* will be moved to >> Kconfig? >> What about #defines that will absolutely never used by anyone else? >> for example, I (may) have a code fragment that distinguishes between >> "CONFIG_CYGNUS" and "CONFIG_NSPLUS"... >> Would these need to be Kconfig? or would that just clutter Kconfig >> with useless entries? > > Well, at some point yes, pretty much everything will be in Kconfig, like > the Linux Kernel does. I suppose one way to think of it is that if it's > not something that should be configured but is rather a property of the > device, it doesn't belong as CONFIG_ it should just be a define in the > header. Take a look at the other NAND drivers which have been converted > and be at least as converted as they are. More conversions are always > appreciated but we have to keep at least a minimal level :) Thanks! > > -- > Tom _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
