From: kbuild test robot <lkp@intel.com>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Daniel Bristot de Oliveira <daniel@bristot.me>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Lutomirski <luto@kernel.org>,
Clark Williams <williams@redhat.com>,
x86@kernel.org
Subject: Re: [PATCH 2/2] trace,x86: Add nmi to the irq_vectors class
Date: Mon, 17 Sep 2018 18:18:13 +0800 [thread overview]
Message-ID: <201809171843.kVNL2mbn%fengguang.wu@intel.com> (raw)
In-Reply-To: <998ff6da1fe084c94cb7eedcee697b7ec1fbd66c.1537173660.git.bristot@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
Hi Daniel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.19-rc4 next-20180913]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Daniel-Bristot-de-Oliveira/trace-x86-Add-external_interrupts-to-the-irq_vectors-class/20180917-173538
config: i386-randconfig-x003-201837 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
arch/x86/kernel/nmi.c: In function 'do_nmi':
>> arch/x86/kernel/nmi.c:519:2: error: implicit declaration of function 'trace_nmi_entry'; did you mean 'ftrace_nmi_enter'? [-Werror=implicit-function-declaration]
trace_nmi_entry(2);
^~~~~~~~~~~~~~~
ftrace_nmi_enter
>> arch/x86/kernel/nmi.c:526:2: error: implicit declaration of function 'trace_nmi_exit'; did you mean 'ftrace_nmi_exit'? [-Werror=implicit-function-declaration]
trace_nmi_exit(2);
^~~~~~~~~~~~~~
ftrace_nmi_exit
cc1: some warnings being treated as errors
vim +519 arch/x86/kernel/nmi.c
517
518 nmi_enter();
> 519 trace_nmi_entry(2);
520
521 inc_irq_stat(__nmi_count);
522
523 if (!ignore_nmis)
524 default_do_nmi(regs);
525
> 526 trace_nmi_exit(2);
527 nmi_exit();
528
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 22639 bytes --]
next prev parent reply other threads:[~2018-09-17 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 8:48 [PATCH 1/2] trace,x86: Add external_interrupts " Daniel Bristot de Oliveira
2018-09-17 8:48 ` [PATCH 2/2] trace,x86: Add nmi " Daniel Bristot de Oliveira
2018-09-17 10:18 ` kbuild test robot [this message]
2018-09-17 10:24 ` [PATCH 1/2] trace,x86: Add external_interrupts " kbuild test robot
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=201809171843.kVNL2mbn%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bristot@redhat.com \
--cc=daniel@bristot.me \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
--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
all inboxes | Powered by JetHome®