On Tue, Aug 09, 2016 at 05:55:08AM +0200, Borislav Petkov wrote: > On Mon, Aug 08, 2016 at 05:05:39PM +0200, Luis R. Rodriguez wrote: > > > So how can I disable those table-* things from even getting built? Avoid > > > using table-y? But then everything declared table-y will be built > > > unconditionally. I don't think I like that. :-\ > > > > I suppose we could make this configurable... But frankly I would prefer to > > instead just document that this use should be carefully considered instead, > > and let this be up to the maintainers. We can make it easily configurable so > > we can do that later becomes a required, I don't think its needed though > > given maintainers should use it only when needed. > > You know how maintainers are just people, right? At least in most cases :-) > > I think it would be better if it were machine-enforceable somehow. > Maybe allow it only for core code and have a single, per-arch file > arch/x86/linker_tables or so where all those statements are collected > and can be eyeballed by more people. Dunno, just trying to think of > something here... OK I've added CONFIG_BUILD_AVOID_BITROT. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
