From: kbuild test robot <lkp@intel.com>
To: Howard Cochran <hcochran@kernelspring.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Howard Cochran <cochran@lexmark.com>,
Howard Cochran <hcochran@kernelspring.com>
Subject: Re: [PATCH 1/5] tracing: Add param to event_trigger_ops.func() for instances
Date: Fri, 15 Apr 2016 15:10:42 +0800 [thread overview]
Message-ID: <201604151543.RiR9Nk6b%fengguang.wu@intel.com> (raw)
In-Reply-To: <1460703230-13307-2-git-send-email-hcochran@kernelspring.com>
[-- Attachment #1: Type: text/plain, Size: 2086 bytes --]
Hi Howard,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.6-rc3 next-20160414]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Howard-Cochran/tracing-Add-param-to-event_trigger_ops-func-for-instances/20160415-145801
config: i386-randconfig-x000-201615 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
Note: the linux-review/Howard-Cochran/tracing-Add-param-to-event_trigger_ops-func-for-instances/20160415-145801 HEAD 30aa67c47e19ac73897f7683d98b7c49a08cf635 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
kernel/trace/trace_events_trigger.c: In function 'snapshot_count_trigger':
>> kernel/trace/trace_events_trigger.c:917:2: error: too few arguments to function 'snapshot_trigger'
snapshot_trigger(data, rec);
^
kernel/trace/trace_events_trigger.c:901:1: note: declared here
snapshot_trigger(struct event_trigger_data *data, void *rec,
^
vim +/snapshot_trigger +917 kernel/trace/trace_events_trigger.c
93e31ffb Tom Zanussi 2013-10-24 911 if (!data->count)
93e31ffb Tom Zanussi 2013-10-24 912 return;
93e31ffb Tom Zanussi 2013-10-24 913
93e31ffb Tom Zanussi 2013-10-24 914 if (data->count != -1)
93e31ffb Tom Zanussi 2013-10-24 915 (data->count)--;
93e31ffb Tom Zanussi 2013-10-24 916
c4a59230 Tom Zanussi 2015-12-10 @917 snapshot_trigger(data, rec);
93e31ffb Tom Zanussi 2013-10-24 918 }
93e31ffb Tom Zanussi 2013-10-24 919
93e31ffb Tom Zanussi 2013-10-24 920 static int
:::::: The code at line 917 was first introduced by commit
:::::: c4a5923055c9e0c87dfc0387f7cda5ee2bbac3c1 tracing: Add event record param to trigger_ops.func()
:::::: TO: Tom Zanussi <tom.zanussi@linux.intel.com>
:::::: CC: Steven Rostedt <rostedt@goodmis.org>
---
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: 21675 bytes --]
next prev parent reply other threads:[~2016-04-15 7:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 6:53 [PATCHSET] tracing: Make event triggers affect correct instance Howard Cochran
2016-04-15 6:53 ` [PATCH 1/5] tracing: Add param to event_trigger_ops.func() for instances Howard Cochran
2016-04-15 7:10 ` kbuild test robot [this message]
2016-04-15 6:53 ` [PATCH 2/5] tracing: Make stacktrace trigger affect the correct instance Howard Cochran
2016-04-15 6:53 ` [PATCH 3/5] tracing: Make traceon, traceoff " Howard Cochran
2016-04-15 6:53 ` [PATCH 4/5] tracing: Make snapshot " Howard Cochran
2016-04-15 6:53 ` [PATCH 5/5] tracing: Make internal_trace_puts() write to " Howard Cochran
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=201604151543.RiR9Nk6b%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=cochran@lexmark.com \
--cc=hcochran@kernelspring.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;
as well as URLs for NNTP newsgroup(s).