From: kbuild test robot <lkp@intel.com>
To: Abderrahmane Benbachir <abderrahmane.benbachir@polymtl.ca>
Cc: kbuild-all@01.org, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, mathieu.desnoyers@efficios.com,
abderb@microsoft.com
Subject: Re: [PATCH v4] ftrace: support early boot function tracing
Date: Mon, 10 Dec 2018 06:05:27 +0800 [thread overview]
Message-ID: <201812100620.RQbAtHXt%fengguang.wu@intel.com> (raw)
In-Reply-To: <6ff3e0c362b5b891b3ce1a3f0b61a34226d95bb0.camel@polymtl.ca>
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
Hi Abderrahmane,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.20-rc5 next-20181207]
[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/Abderrahmane-Benbachir/ftrace-support-early-boot-function-tracing/20181209-130427
config: i386-randconfig-s0-12100145 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from include/linux/perf_event.h:48:0,
from include/linux/trace_events.h:10,
from include/trace/syscall.h:7,
from include/linux/syscalls.h:85,
from kernel/fork.c:52:
include/linux/ftrace.h: In function 'ftrace_init':
>> include/linux/ftrace.h:735:40: error: implicit declaration of function 'ftrace_early_shutdown' [-Werror=implicit-function-declaration]
static inline void ftrace_init(void) { ftrace_early_shutdown(); }
^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/ftrace_early_shutdown +735 include/linux/ftrace.h
731
732 #ifdef CONFIG_FTRACE_MCOUNT_RECORD
733 extern void ftrace_init(void);
734 #else
> 735 static inline void ftrace_init(void) { ftrace_early_shutdown(); }
736 #endif
737
---
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: 32198 bytes --]
prev parent reply other threads:[~2018-12-09 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 8:35 Abderrahmane Benbachir
2018-12-09 6:22 ` kbuild test robot
2018-12-09 22:05 ` kbuild test robot [this message]
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=201812100620.RQbAtHXt%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=abderb@microsoft.com \
--cc=abderrahmane.benbachir@polymtl.ca \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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®