linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Prarit Bhargava <prarit@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Len Brown <len.brown@intel.com>, Borislav Petkov <bp@suse.de>,
	Andi Kleen <ak@linux.intel.com>, Jiri Olsa <jolsa@redhat.com>,
	Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH 1/2] drivers/base: Combine topology.c and cpu.c
Date: Wed, 7 Sep 2016 21:31:06 +0800	[thread overview]
Message-ID: <201609072110.J3Aj1xoF%fengguang.wu@intel.com> (raw)
In-Reply-To: <1473248657-17359-2-git-send-email-prarit@redhat.com>

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

Hi Prarit,

[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on v4.8-rc5 next-20160907]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]

url:    https://github.com/0day-ci/linux/commits/Prarit-Bhargava/cpu-hotplug-keep-topology-directory-after-soft-remove-event/20160907-210020
config: x86_64-randconfig-x015-201636 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

>> drivers/base/cpu.c:260:11: error: 'topology_attrs' undeclared here (not in a function)
     .attrs = topology_attrs,
              ^~~~~~~~~~~~~~

vim +/topology_attrs +260 drivers/base/cpu.c

   254	static struct attribute_group crash_note_cpu_attr_group = {
   255		.attrs = crash_note_cpu_attrs,
   256	};
   257	#endif
   258	
   259	static struct attribute_group topology_attr_group = {
 > 260		.attrs = topology_attrs,
   261		.name = "topology"
   262	};
   263	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 28487 bytes --]

  reply	other threads:[~2016-09-07 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 11:44 [PATCH 0/2] cpu hotplug, keep topology directory after soft remove event Prarit Bhargava
2016-09-07 11:44 ` [PATCH 1/2] drivers/base: Combine topology.c and cpu.c Prarit Bhargava
2016-09-07 13:31   ` kbuild test robot [this message]
2016-09-07 11:44 ` [PATCH 2/2] cpu hotplug, add CONFIG_PERMANENT_CPU_TOPOLOGY Prarit Bhargava
2016-09-08  7:45   ` Peter Zijlstra
2016-09-08 13:45     ` Prarit Bhargava

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=201609072110.J3Aj1xoF%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=ak@linux.intel.com \
    --cc=bp@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=jolsa@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=prarit@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).