mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: kbuild-all@01.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Tony Luck <tony.luck@intel.com>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <peterz@infradead.org>,
	David Rientjes <rientjes@google.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Prarit Bhargava <prarit@redhat.com>,
	brice.goglin@gmail.com, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] x86,sched: allow topologies where NUMA nodes share an LLC
Date: Fri, 30 Mar 2018 11:20:55 +0800	[thread overview]
Message-ID: <201803301038.kA7Jkdch%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180329000024.GA16648@alison-desk.jf.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

Hi Alison,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on v4.16-rc7]
[also build test WARNING on next-20180329]
[cannot apply to tip/x86/core]
[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/Alison-Schofield/x86-sched-allow-topologies-where-NUMA-nodes-share-an-LLC/20180330-070743
config: x86_64-allyesdebian (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

>> WARNING: vmlinux.o(.text+0x9601e): Section mismatch in reference from the function set_cpu_sibling_map() to the variable .init.rodata:snc_cpu
   The function set_cpu_sibling_map() references
   the variable __initconst snc_cpu.
   This is often because set_cpu_sibling_map lacks a __initconst
   annotation or the annotation of snc_cpu 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: 40066 bytes --]

  parent reply	other threads:[~2018-03-30  3:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29  0:00 Alison Schofield
2018-03-29 13:16 ` Thomas Gleixner
2018-03-29 13:45   ` Dave Hansen
2018-03-29 13:57     ` Peter Zijlstra
2018-03-29 13:47   ` Peter Zijlstra
2018-03-29 14:34     ` Dave Hansen
2018-03-29 16:09       ` Peter Zijlstra
2018-03-29 16:25         ` Dave Hansen
2018-03-29 16:29           ` Luck, Tony
2018-03-29 14:37     ` Dave Hansen
2018-03-29 14:55       ` Peter Zijlstra
2018-03-30  3:20 ` kbuild test robot [this message]
2018-03-30 17:34 ` Alison Schofield

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=201803301038.kA7Jkdch%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=bp@alien8.de \
    --cc=brice.goglin@gmail.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@linux.intel.com \
    --cc=imammedo@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=prarit@redhat.com \
    --cc=rientjes@google.com \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@linux.intel.com \
    --cc=tony.luck@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®