On Fri, May 03, 2013 at 05:10:15PM +0200, Michal Marek wrote:
> You still risk that you miss some new dependency, but for a normal
> configs as a base, this won't be an issue in most cases. Whether this is
> implemented as a series of scripts/config calls or if there is a
> kvm_guest.config does not matter much, as long as randconfig does not
> see it ;).
Yep, I think we can do something along the lines of what hpa suggested:
* put a kvm_guest.config in arch/x86/configs/
* teach scripts/config/ to parse it and do set_var() for each line in
there.
* yes "" | make oldconfig - because we want to use the current config
as a base.
I think this is the easiest and cleanest of them all.
--
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
|