[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] linux-next: build failure after merge of the xen-two tree
Konrad Rzeszutek Wilk wrote: > On Fri, Feb 15, 2013 at 03:45:51PM +1100, Stephen Rothwell wrote: >> Hi Konrad, >> >> After merging the xen-two tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: > > Good morning! >> >> drivers/xen/xen-acpi-memhotplug.c: In function >> 'acpi_memory_get_device': >> drivers/xen/xen-acpi-memhotplug.c:191:2: error: implicit declaration >> of function 'acpi_bus_add' [-Werror=implicit-function-declaration] >> drivers/xen/xen-acpi-memhotplug.c: At top level: >> drivers/xen/xen-acpi-memhotplug.c:417:3: warning: initialization >> from incompatible pointer type [enabled by default] >> drivers/xen/xen-acpi-memhotplug.c:417:3: warning: (near >> initialization for 'xen_acpi_memory_device_driver.ops.remove') >> [enabled by default] >> >> Caused by commit 259f201cb7ea ("xen/acpi: ACPI memory hotplug"). >> >> drivers/xen/xen-acpi-cpuhotplug.c: In function >> 'acpi_processor_device_add': >> drivers/xen/xen-acpi-cpuhotplug.c:254:2: error: implicit declaration >> of function 'acpi_bus_add' [-Werror=implicit-function-declaration] >> drivers/xen/xen-acpi-cpuhotplug.c: At top level: >> drivers/xen/xen-acpi-cpuhotplug.c:425:3: warning: initialization >> from incompatible pointer type [enabled by default] >> drivers/xen/xen-acpi-cpuhotplug.c:425:3: warning: (near >> initialization for 'xen_acpi_processor_driver.ops.remove') [enabled >> by default] >> >> Caused by commit 181232c249f0 ("xen/acpi: ACPI cpu hotplug"). > > Grrrreat! Jinsong, can you please fix that ? A patch on top of the > #linux-next > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Done, warning fixed. Thanks, Jinsong _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |