From: kbuild test robot <lkp@intel.com>
To: Piotr Henryk Dabrowski <ultr@ultr.pl>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Piotr Henryk Dabrowski <ultr@ultr.pl>
Subject: Re: [PATCH v2] cpu-= command line parmeter, SYS_cpuid sys call, kernel-adjusted CPUID
Date: Fri, 11 Mar 2016 08:25:34 +0800 [thread overview]
Message-ID: <201603110848.mrCexRrH%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160311011331.52807032@ultra.tux-net>
[-- Attachment #1: Type: text/plain, Size: 1722 bytes --]
Hi Piotr,
[auto build test ERROR on next-20160310]
[cannot apply to tip/x86/core xen-tip/linux-next v4.5-rc7 v4.5-rc6 v4.5-rc5 v4.5-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Piotr-Henryk-Dabrowski/cpu-command-line-parmeter-SYS_cpuid-sys-call-kernel-adjusted-CPUID/20160311-081546
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/kernel/cpu/common.c: In function 'print_forcefully_ignored_caps':
>> arch/x86/kernel/cpu/common.c:172:8: error: 'x86_cap_flags' undeclared (first use in this function)
if (x86_cap_flags[bit] != NULL)
^
arch/x86/kernel/cpu/common.c:172:8: note: each undeclared identifier is reported only once for each function it appears in
arch/x86/kernel/cpu/common.c: In function 'setup_forcefully_ignore_caps':
arch/x86/kernel/cpu/common.c:224:7: error: 'x86_cap_flags' undeclared (first use in this function)
if (x86_cap_flags[bit] != NULL) {
^
vim +/x86_cap_flags +172 arch/x86/kernel/cpu/common.c
166
167 buf[0] = '\0';
168 for (bit = 0; bit < 32 * NCAPINTS; bit++)
169 {
170 if (test_bit(bit, (unsigned long *)forcefully_ignored_caps)) {
171 int len = strlen(buf);
> 172 if (x86_cap_flags[bit] != NULL)
173 snprintf(buf + len, sizeof(buf) - len,
174 " %s", x86_cap_flags[bit]);
175 else
---
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: 6269 bytes --]
next prev parent reply other threads:[~2016-03-11 0:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 20:27 [PATCH] cpu-= command line parmeter, SYS_cpuid sys call, kernel-adjusted CPUID Piotr Henryk Dabrowski
2016-03-10 20:38 ` kbuild test robot
2016-03-10 21:08 ` kbuild test robot
2016-03-10 22:27 ` kbuild test robot
2016-03-11 0:13 ` [PATCH v2] " Piotr Henryk Dabrowski
2016-03-11 0:25 ` kbuild test robot [this message]
2016-03-11 0:52 ` kbuild test robot
2016-03-12 1:12 ` [PATCH v3] " Piotr Henryk Dabrowski
2016-03-12 19:31 ` Henrique de Moraes Holschuh
2016-03-14 16:06 ` Piotr Henryk Dabrowski
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=201603110848.mrCexRrH%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ultr@ultr.pl \
/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).