On Fri, 2010-06-04 at 00:17 +0300, Tony Lindgren wrote:
quoted text
> * Linus Torvalds <torvalds@linux-foundation.org> [100603 23:30]:
> > 
> > and now you'd be able to basically generate a OMAP3EVM .config file by 
> > just running "allnoconfig" on that Kconfig.omap3_evm file. But it would 
> > only have to select the parts that are specific for the EVM platform, 
> > because the generic OMAP3 support would be picked by the Kconfig.omap3 
> > file, which in turn would not have to worry about the generic ARM parts 
> > etc.
> > 
> > See?
> 
> Sounds like a good improvment to me.

I was looking at this new defconfig added this merge window,
omap3_stalker_lks_defconig ..

diff -u arch/arm/configs/omap3_defconfig arch/arm/configs/omap3_stalker_lks_defconfig | diffstat
 omap3_stalker_lks_defconfig |  850 +++++++-------------------------------------
 1 file changed, 140 insertions(+), 710 deletions(-)

There's a lot of stuff that's different in there .. If I look through
it, there's stuff that's not related to OMAP , or even drivers. Like
Kprobes gets disabled over omap3_defconfig .

To me that's kind of messy .. It should really be just what the user
absolutely needs. I think we're able to get away with that now cause no
one cares enough to really read the defconfig and see what's going on.

Having stuff like that adds more flux.

Whatever scheme we go to would likely change that and people would
actually read what's going on. So we wouldn't be able to randomly have
Kprobes enabled in one config, and not enabled in another one. Or having
a debug config as one, then having a performance config for another.

Daniel



--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/