We can put a config file upstream, too. Borislav Petkov <bp@xxxxxxxxx> wrote: >On Fri, May 03, 2013 at 07:54:36AM -0700, Randy Dunlap wrote: >> Could you alternately have a kvm_guest.config that should always work >> for you? > >I could, and I do. The idea, however, is to have this option upstream >so that people don't have to go search for every relevant option for >running the kernel a kvm guest. > >Which reminds me: Pekka had a 'make kvmconfig' functionality in >the kvmtool too. Which, TBH, is even better than having a Kconfig >option with a bunch of selects. So, come to think of it, after all >the controversy with such an option, having a 'make kvmconfig' do >scripts/config -e <option> where <option> is in that list we select >would be much better. > >This won't break randconfigs at all, btw. :-) > >Michal? -- Sent from my mobile phone. Please excuse brevity and lack of formatting. -- 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
|