On Mon, Feb 17, 2014 at 09:50:40AM +0100, Paul Bolle wrote: > On Mon, 2014-02-17 at 09:20 +0100, Heiko Carstens wrote: > > On Sun, Feb 16, 2014 at 06:15:27PM +0100, Paul Bolle wrote: > > No, I want to keep them, so there is a config symbol for each cpu generation > > and we don't have to add the config symbols again, if we actually use them. > > Yes, that's the idea: only add Kconfig symbols that you are actually > going to use. > > > It's a question of completeness in this case, not if they are being used. > > Completeness of what?
Each cpu generation we support is supposed to have a "HAVE_MARCH_<GENERATION>_FEATURES" config symbol. > Anyhow, perhaps you can comment this stuff out if you want to have it in > the tree. See, these symbols will pop up each time that people run their > scripts to discover problems in the kconfig space. I suppose this was > probably not the first time these two were reported. And people not > aware of this thread might do that again, and again... What script did you use? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
