From: kbuild test robot <lkp@intel.com>
To: Chunyu Hu <chuhu@redhat.com>
Cc: kbuild-all@01.org, rostedt@goodmis.org, liwan@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tracing: make tracer_flags use the right set_flag callback
Date: Tue, 8 Mar 2016 21:51:29 +0800 [thread overview]
Message-ID: <201603082107.0qqLBQZ7%fengguang.wu@intel.com> (raw)
In-Reply-To: <1457444222-8654-1-git-send-email-chuhu@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2106 bytes --]
Hi Chunyu,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.5-rc7 next-20160308]
[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/Chunyu-Hu/tracing-make-tracer_flags-use-the-right-set_flag-callback/20160308-214136
config: i386-randconfig-x000-201610 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/trace/trace.c: In function 'create_trace_option_files':
>> kernel/trace/trace.c:6403:7: error: 'i' undeclared (first use in this function)
for (i = 0; i < tr->nr_topts; i++) {
^
kernel/trace/trace.c:6403:7: note: each undeclared identifier is reported only once for each function it appears in
vim +/i +6403 kernel/trace/trace.c
37aea98b Steven Rostedt (Red Hat 2015-09-30 6397) * If this is an instance, only create flags for tracers
37aea98b Steven Rostedt (Red Hat 2015-09-30 6398) * the instance may have.
37aea98b Steven Rostedt (Red Hat 2015-09-30 6399) */
37aea98b Steven Rostedt (Red Hat 2015-09-30 6400) if (!trace_ok_for_array(tracer, tr))
37aea98b Steven Rostedt (Red Hat 2015-09-30 6401) return;
37aea98b Steven Rostedt (Red Hat 2015-09-30 6402)
37aea98b Steven Rostedt (Red Hat 2015-09-30 @6403) for (i = 0; i < tr->nr_topts; i++) {
37aea98b Steven Rostedt (Red Hat 2015-09-30 6404) /*
37aea98b Steven Rostedt (Red Hat 2015-09-30 6405) * Check if these flags have already been added.
37aea98b Steven Rostedt (Red Hat 2015-09-30 6406) * Some tracers share flags.
:::::: The code at line 6403 was first introduced by commit
:::::: 37aea98b84c0ce2ac638510fefeed9f8f920bd34 tracing: Add trace options for tracer options to instances
:::::: TO: Steven Rostedt (Red Hat) <rostedt@goodmis.org>
:::::: 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: 23390 bytes --]
next prev parent reply other threads:[~2016-03-08 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 13:37 Chunyu Hu
2016-03-08 13:37 ` [PATCH 2/2] tracing: fix typoes in code comment and printk in trace_nop.c Chunyu Hu
2016-03-08 13:51 ` kbuild test robot [this message]
2016-03-08 14:15 ` [PATCH 1/2] tracing: make tracer_flags use the right set_flag callback Steven Rostedt
2016-03-08 14:33 ` Steven Rostedt
2016-03-08 15:22 ` Chunyu Hu
2016-03-08 15:32 ` Steven Rostedt
2016-03-08 15:33 ` Steven Rostedt
2016-03-08 15:36 ` Steven Rostedt
2016-03-08 14:54 ` Steven Rostedt
2016-03-08 15:14 ` Steven Rostedt
2016-03-08 15:55 ` Chunyu Hu
2016-03-08 16:23 ` Steven Rostedt
2016-03-09 13:38 ` Chunyu Hu
2016-03-09 13:52 ` Steven Rostedt
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=201603082107.0qqLBQZ7%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=chuhu@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwan@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®