From: kbuild test robot <fengguang.wu@intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Thomas Gleixner <tglx@linutronix.de>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
jgross@suse.com
Subject: [tip:smp/hotplug 5/6] arch/x86/xen/enlighten.c:1522:2: error: implicit declaration of function 'xen_pvh_early_cpu_init'
Date: Fri, 29 Jul 2016 00:14:46 +0800 [thread overview]
Message-ID: <201607290042.Cg7WolYT%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/hotplug
head: c713c8cb2055f5f3b32ee4315be589177a2658cc
commit: 854e9fa5a56a9771fad4701a427e4844d2cbade1 [5/6] xen/x86: Define stubs for xen_smp_intr_init/xen_smp_intr_free
config: x86_64-randconfig-x011-201630 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
git checkout 854e9fa5a56a9771fad4701a427e4844d2cbade1
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
arch/x86/xen/enlighten.c: In function 'xen_pvh_early_guest_init':
>> arch/x86/xen/enlighten.c:1522:2: error: implicit declaration of function 'xen_pvh_early_cpu_init' [-Werror=implicit-function-declaration]
xen_pvh_early_cpu_init(0, false);
^~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/xen_pvh_early_cpu_init +1522 arch/x86/xen/enlighten.c
d285d683 Mukesh Rathor 2013-12-13 1516
c9f6e997 Roger Pau Monne 2014-01-20 1517 if (!xen_feature(XENFEAT_hvm_callback_vector))
c9f6e997 Roger Pau Monne 2014-01-20 1518 return;
c9f6e997 Roger Pau Monne 2014-01-20 1519
d285d683 Mukesh Rathor 2013-12-13 1520 xen_have_vector_callback = 1;
a2ef5dc2 Mukesh Rathor 2014-09-10 1521
a2ef5dc2 Mukesh Rathor 2014-09-10 @1522 xen_pvh_early_cpu_init(0, false);
c9f6e997 Roger Pau Monne 2014-01-20 1523 xen_pvh_set_cr_flags(0);
d285d683 Mukesh Rathor 2013-12-13 1524
d285d683 Mukesh Rathor 2013-12-13 1525 #ifdef CONFIG_X86_32
:::::: The code at line 1522 was first introduced by commit
:::::: a2ef5dc2c7cbedbeb4c847039845afaea5e63745 x86/xen: Set EFER.NX and EFER.SCE in PVH guests
:::::: TO: Mukesh Rathor <mukesh.rathor@oracle.com>
:::::: CC: David Vrabel <david.vrabel@citrix.com>
---
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: 26458 bytes --]
next reply other threads:[~2016-07-28 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 16:14 kbuild test robot [this message]
2016-07-29 2:03 ` 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=201607290042.Cg7WolYT%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.com \
/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®