Some more comments. > - your patches might break apps/ABI
Can you please explain that a bit more. We have a lot of CONFIG options that disable syscalls, /sys, lots of stuff. Whoever uses them needs to know what they are doing. I thought it was pretty much consensus that Linux is supposed to be a very configurable OS, which people can taylor from small embedded to large kitchen sink included using CONFIG_*. Are you saying that Linux should not be configurable small to big? (I would find that hard to believe). If that's really your standpoint I would like to see some confirmation on this, as it would seem a big departure from traditional practice. Or is the concern that you want it default y or EXPERT, so what the defaults are? That sounds reasonable. Or should it be more modular like Peter pointed out (that would seem like a good solution for generic distros, but not so good for deeply embedded like running on Quark) BTW afaik pretty much every other architecture still allows to disable it, just x86 has this dependency loop problem. > > - your patch-set unnecessarily complicates things, making the kernel > less maintainable I actually simplified some things, like unnecessary dependencies between perf and profile. These should be applied in any case as they are independent. I can repost them. Given some of the ifdefs/configs were not nice, perhaps there's a better solution for this from Frederic. -Andi -- 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/
