From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, rjw@rjwysocki.net, len.brown@intel.com,
pavel@ucw.cz, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, x86@kernel.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] ACPI/NUMA: Do not map pxm to node when NUMA is turned off
Date: Tue, 13 Dec 2016 08:11:25 +0800 [thread overview]
Message-ID: <201612130824.Azkdzfm2%fengguang.wu@intel.com> (raw)
In-Reply-To: <1481570993-13941-2-git-send-email-boris.ostrovsky@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
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
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37778 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: kbuild-all@01.org, rjw@rjwysocki.net, len.brown@intel.com,
pavel@ucw.cz, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, x86@kernel.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] ACPI/NUMA: Do not map pxm to node when NUMA is turned off
Date: Tue, 13 Dec 2016 08:11:25 +0800 [thread overview]
Message-ID: <201612130824.Azkdzfm2%fengguang.wu@intel.com> (raw)
In-Reply-To: <1481570993-13941-2-git-send-email-boris.ostrovsky@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
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
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37778 bytes --]
next prev parent reply other threads:[~2016-12-13 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 19:29 [PATCH] x86/acpi: Use proper macro for invalid node Boris Ostrovsky
2016-12-12 19:29 ` [PATCH] ACPI/NUMA: Do not map pxm to node when NUMA is turned off Boris Ostrovsky
2016-12-13 0:11 ` kbuild test robot [this message]
2016-12-13 0:11 ` kbuild test robot
2016-12-15 11:52 ` [tip:x86/urgent] x86/acpi: Use proper macro for invalid node tip-bot for Boris Ostrovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201612130824.Azkdzfm2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.