On Wed, May 01, 2013 at 03:09:13PM -0700, David Rientjes wrote: > Unfortunately, the way you're implementing KVM_GUEST_COMMON_OPTIONS > will typically result in this if the options you "select" get new > dependencies in the future. So you'll always be updating this option > constantly with these types of problems. Ok, so let's step back a bit here: I've added this option with the idea to have it as a shortcut so that you don't go search for every commodity option when you want to boot the kernel as a kvm guest. Currently I have it in all.config when doing randconfig builds here. While I'm doing the randbuilds, why not boot it in kvm too while at it. Now, I really fail to see what you describe above to be a fairly normal use case. I'm sure you can take Kconfig and abuse it so that it screams all kinds of errors and we know select is evil and Kconfig is not perfect, etc, etc... So I'm pretty sure we won't be able to plug all holes. However, let's try to plug only those which hinder *real* usage instead of contrived stuff. So, let's start again: is this something real you're triggering with some random testing you're doing or are you simply abusing^Wexperimenting with Kconfig and staring at what breaks? Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html