From: kbuild test robot <lkp@intel.com>
To: Dmitry Safonov <0x7f454c46@gmail.com>
Cc: kbuild-all@01.org, rostedt@goodmis.org, mingo@redhat.com,
linux-kernel@vger.kernel.org,
Dmitry Safonov <0x7f454c46@gmail.com>
Subject: Re: [PATCH] trace_functions_graph: Remove __trace_graph_function
Date: Sat, 31 Oct 2015 03:18:31 +0800 [thread overview]
Message-ID: <201510310304.ImOVRlgO%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446232038-27113-1-git-send-email-0x7f454c46@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
Hi Dmitry,
[auto build test ERROR on v4.3-rc7 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
url: https://github.com/0day-ci/linux/commits/Dmitry-Safonov/trace_functions_graph-Remove-__trace_graph_function/20151031-030819
config: x86_64-randconfig-x014-10300134 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> kernel/trace/trace_functions_graph.c:363:6: error: conflicting types for 'trace_graph_function'
void trace_graph_function(struct trace_array *tr,
^
In file included from kernel/trace/trace_functions_graph.c:14:0:
kernel/trace/trace.h:578:6: note: previous declaration of 'trace_graph_function' was here
void trace_graph_function(struct trace_array *tr,
^
vim +/trace_graph_function +363 kernel/trace/trace_functions_graph.c
357 if (tracing_thresh)
358 return 1;
359 else
360 return trace_graph_entry(trace);
361 }
362
> 363 void trace_graph_function(struct trace_array *tr,
364 unsigned long ip, unsigned long flags, int pc)
365 {
366 u64 time = trace_clock_local();
---
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: 22003 bytes --]
prev parent reply other threads:[~2015-10-30 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 19:07 Dmitry Safonov
2015-10-30 19:18 ` Dmitry Safonov
2015-10-30 19:19 ` Dmitry Safonov
2015-10-30 19:18 ` 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=201510310304.ImOVRlgO%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=0x7f454c46@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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®