From: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Petr Tesarik <ptesarik@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 9661/9894] arch/x86/xen/enlighten.c:1328:2: note: in expansion of macro 'if'
Date: Thu, 14 Jul 2016 19:39:43 +0800 [thread overview]
Message-ID: <201607141941.aof4pvNe%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: fd8d43a58dacbbde8beaaecbeaed7bd8bdbe6859
commit: 01eff0378a46a33a1252f9a3a4817263e16f52c0 [9661/9894] kexec: allow kdump with crash_kexec_post_notifiers
config: x86_64-randconfig-i0-201628 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
git checkout 01eff0378a46a33a1252f9a3a4817263e16f52c0
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
In file included from include/linux/ioport.h:12:0,
from include/linux/device.h:16,
from include/linux/node.h:17,
from include/linux/cpu.h:16,
from arch/x86/xen/enlighten.c:14:
arch/x86/xen/enlighten.c: In function 'xen_panic_event':
arch/x86/xen/enlighten.c:1328:7: error: implicit declaration of function 'kexec_crash_loaded' [-Werror=implicit-function-declaration]
if (!kexec_crash_loaded())
^
include/linux/compiler.h:151:30: note: in definition of macro '__trace_if'
if (__builtin_constant_p(!!(cond)) ? !!(cond) : \
^~~~
>> arch/x86/xen/enlighten.c:1328:2: note: in expansion of macro 'if'
if (!kexec_crash_loaded())
^~
cc1: some warnings being treated as errors
vim +/if +1328 arch/x86/xen/enlighten.c
1312
1313 static void xen_machine_power_off(void)
1314 {
1315 if (pm_power_off)
1316 pm_power_off();
1317 xen_reboot(SHUTDOWN_poweroff);
1318 }
1319
1320 static void xen_crash_shutdown(struct pt_regs *regs)
1321 {
1322 xen_reboot(SHUTDOWN_crash);
1323 }
1324
1325 static int
1326 xen_panic_event(struct notifier_block *this, unsigned long event, void *ptr)
1327 {
> 1328 if (!kexec_crash_loaded())
1329 xen_reboot(SHUTDOWN_crash);
1330 return NOTIFY_DONE;
1331 }
1332
1333 static struct notifier_block xen_panic_block = {
1334 .notifier_call= xen_panic_event,
1335 .priority = INT_MIN
1336 };
---
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: 25094 bytes --]
next reply other threads:[~2016-07-14 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 11:39 kbuild test robot [this message]
2016-07-14 20:02 ` Andrew Morton
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=201607141941.aof4pvNe%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=ptesarik@suse.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