On Fri, Jan 05, 2018 at 09:54:45PM +0100, Greg Kroah-Hartman wrote: > On Fri, Jan 05, 2018 at 09:56:16AM -0800, Guenter Roeck wrote: > > On Wed, Jan 03, 2018 at 09:11:06PM +0100, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 4.4.110 release. > > > There are 37 patches in this series, all will be posted as a response > > > to this one. If anyone has any issues with these being applied, please > > > let me know. > > > > > > Responses should be made by Fri Jan 5 19:50:38 UTC 2018. > > > Anything received after that time might be too late. > > > > > > > Update: v4.4.110 final nosmp builds fail as follows: > > > > ------------ > > Error log: > > arch/x86/entry/vdso/vma.c: In function ‘map_vdso’: > > arch/x86/entry/vdso/vma.c:173:9: error: > > implicit declaration of function ‘pvclock_pvti_cpu0_va’ > > x86-64 or i386? x86-64 > That should be a CONFIG_PARAVIRT_CLOCK issue, not a smp build issue, > have a .config I can try? > https://github.com/groeck/linux-build-test/blob/master/rootfs/x86_64/qemu_x86_64_pc_nosmp_defconfig However, https://github.com/groeck/linux-build-test/blob/master/rootfs/x86_64/qemu_x86_64_pc_defconfig does build, and the only differences are: 30a31 > CONFIG_SMP=y 32a34,35 > CONFIG_NR_CPUS=24 > CONFIG_SCHED_SMT=y 44d46 < CONFIG_ACPI_CONTAINER=y Both configurations have CONFIG_PARAVIRT_CLOCK disabled. Guenter