On 11/04/2011 01:03 PM, Pekka Enberg wrote: > On Fri, Nov 4, 2011 at 6:59 PM, Randy Dunlap <rdunlap@xxxxxxxxxxxx> wrote: >> On 11/03/2011 05:43 PM, Randy Dunlap wrote: >>> On 11/02/2011 11:20 PM, Stephen Rothwell wrote: >>>> Hi all, >>> >>> >>> When KVMTOOL_TEST_ENABLE is enabled but CONFIG_BLOCK is not enabled, there are >>> MANY build errors. This one (case) is probably fixed by adding "select BLOCK", but it's >>> all rather ugly. >> >> kconfig even tells us: >> >> warning: (KVMTOOL_TEST_ENABLE) selects KGDB which has unmet direct dependencies (HAVE_ARCH_KGDB && DEBUG_KERNEL && EXPERIMENTAL) >> warning: (KVMTOOL_TEST_ENABLE) selects BLK_DEV which has unmet direct dependencies (BLOCK) > > Sasha, I guess your patch fixes this? Can you send me a version that > doesn't add the oldconfig magic that Ingo objected to? Here is more of the twisty maze (from linux-next 2011-1107): warning: (KVMTOOL_TEST_ENABLE && AMD_IOMMU) selects PCI_MSI which has unmet direct dependencies (PCI && ARCH_SUPPORTS_MSI) warning: (KVMTOOL_TEST_ENABLE) selects KGDB which has unmet direct dependencies (HAVE_ARCH_KGDB && DEBUG_KERNEL && EXPERIMENTAL) -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
