On Fri, Jun 15, 2012 at 07:24:59PM -0400, Steven Rostedt wrote: > The make target 'oldnoconfig' is a misnomer. It doesn't set new symbols > to 'n', but instead sets it to their default values. > > Unfortunately, assuming that it actually did this, broke ktest in some > of its tests. For example, the tests to create a minimum config and even > a config bisect, depends on removing various configs and using > oldnoconfig to get rid of other configs that may have depended on it. > > But because some configs that it was trying to disable, were in fact > default enabled, this caused those configs to re-enable and corrupt the > test. > > I thought about fixing oldnoconfig, but I'm afraid that people are > already dependent on its current behavior. Instead, I'm just updating > the documentation to state that it sets the new symbols to their default > values and not to 'n'. > > Ideally, this would be called, 'olddefconfig' and we have an > 'oldnoconfig' that actually disables the new symbols. But it's useless > for me now. If it changed, ktest would need to be consistent between > each version, and that would be to difficult to detect. I'll handle this > issue with ktest with other means. > > Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx> Applied to kbuild.git#kconfig, thanks. Michal -- 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
