On Tue, Dec 15, 2015 at 8:32 AM, Jim Davis <jim.epost@xxxxxxxxx> wrote: > Building with the attached random configuration file, > > arch/x86/built-in.o: In function `map_vdso': > vma.c:(.text+0x13fc): undefined reference to `pvclock_pvti_cpu0_va' Whoops, thanks! I confused CONFIG_PARAVIRT_CLOCK and CONFIG_KVM_GUEST. Ingo, what should I do? AFAICS these aren't currently in -tip or queued for -next at all. Should I send a fixup on top of the pending patches? Should I resend both series, with this problem fixed, merged into one bigger series? --Andy > > > -- > Jim -- Andy Lutomirski AMA Capital Management, LLC -- 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
