[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201612130824.Azkdzfm2%fengguang.wu@intel.com>
Date: Tue, 13 Dec 2016 08:11:25 +0800
From: kbuild test robot <lkp@...el.com>
To: Boris Ostrovsky <boris.ostrovsky@...cle.com>
Cc: kbuild-all@...org, rjw@...ysocki.net, len.brown@...el.com,
pavel@....cz, tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
x86@...nel.org, Boris Ostrovsky <boris.ostrovsky@...cle.com>
Subject: Re: [PATCH] ACPI/NUMA: Do not map pxm to node when NUMA is turned off
Hi Boris,
[auto build test WARNING on pm/linux-next]
[also build test WARNING on v4.9 next-20161212]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Boris-Ostrovsky/ACPI-NUMA-Do-not-map-pxm-to-node-when-NUMA-is-turned-off/20161213-045302
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: x86_64-allyesdebian (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
>> WARNING: vmlinux.o(.text+0x8acd33): Section mismatch in reference from the function acpi_map_pxm_to_node() to the variable .init.data:numa_off
The function acpi_map_pxm_to_node() references
the variable __initdata numa_off.
This is often because acpi_map_pxm_to_node lacks a __initdata
annotation or the annotation of numa_off is wrong.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Download attachment ".config.gz" of type "application/gzip" (37778 bytes)
Powered by blists - more mailing lists