public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: kbuild test robot <lkp@intel.com>
Cc: <kbuild-all@01.org>, <tglx@linutronix.de>, <mingo@redhat.com>,
	<hpa@zytor.com>, <bp@suse.de>, <x86@kernel.org>,
	<sudeep.holla@arm.com>, <akpm@linux-foundation.org>,
	<geliangtang@163.com>, <tj@kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/intel_cacheinfo: Fix LLC topology for AMD Fam17h systems
Date: Tue, 3 Nov 2015 13:41:53 -0600	[thread overview]
Message-ID: <56390E01.6050104@amd.com> (raw)
In-Reply-To: <201511040312.OQPDNtTX%fengguang.wu@intel.com>

On 11/3/2015 1:27 PM, kbuild test robot wrote:
> Hi Aravind,
>
> [auto build test ERROR on bp/for-next]
> [also ERROR on: v4.3 next-20151103]
>
> url:    https://github.com/0day-ci/linux/commits/Aravind-Gopalakrishnan/x86-intel_cacheinfo-Fix-LLC-topology-for-AMD-Fam17h-systems/20151104-031725
> base:   https://github.com/0day-ci/linux Aravind-Gopalakrishnan/x86-intel_cacheinfo-Fix-LLC-topology-for-AMD-Fam17h-systems/20151104-031725
> config: i386-tinyconfig (attached as .config)
> reproduce:
>          # save the attached .config to linux build tree
>          make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
>     arch/x86/built-in.o: In function `init_amd_cacheinfo':
>>> (.text+0x6aec): undefined reference to `cpu_llc_id'
>

Thanks for the catch!

cpu_llc_id references should be wrapped under #ifdef CONFIG_SMP.

Did that and kernel build worked with the attached config.

Will send a V2 with the fix.

Thanks,
-Aravind.

  reply	other threads:[~2015-11-03 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 19:15 [PATCH] x86/intel_cacheinfo: Fix LLC topology for AMD Fam17h systems Aravind Gopalakrishnan
2015-11-03 19:27 ` kbuild test robot
2015-11-03 19:41   ` Aravind Gopalakrishnan [this message]
2015-11-03 19:52     ` Borislav Petkov
2015-11-03 19:58       ` Aravind Gopalakrishnan

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=56390E01.6050104@amd.com \
    --to=aravind.gopalakrishnan@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=geliangtang@163.com \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@redhat.com \
    --cc=sudeep.holla@arm.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --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