From: kbuild test robot <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@01.org,
Linux Memory Management List <linux-mm@kvack.org>,
mmotm auto import <mm-commits@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: [mmotm:master 277/310] kernel/trace/trace_functions_graph.c:173:27: error: 'struct ftrace_ret_stack' has no member named 'subtime'; did you mean 'calltime'?
Date: Wed, 5 Oct 2016 07:35:53 +0800 [thread overview]
Message-ID: <201610050750.gvhXrSoc%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: b9215f97283c8239d33a0ea59d0a7ce7060a7255
commit: 05fd6fa64d9f004ab1321df8d5640e301ab48bc5 [277/310] linux-next-git-rejects
config: x86_64-allyesdebian (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout 05fd6fa64d9f004ab1321df8d5640e301ab48bc5
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
kernel/trace/trace_functions_graph.c: In function 'ftrace_push_return_trace':
>> kernel/trace/trace_functions_graph.c:173:27: error: 'struct ftrace_ret_stack' has no member named 'subtime'; did you mean 'calltime'?
current->ret_stack[index].subtime = 0;
^
vim +173 kernel/trace/trace_functions_graph.c
29ad23b0 Namhyung Kim 2013-10-14 167 if (ftrace_graph_notrace_addr(func))
29ad23b0 Namhyung Kim 2013-10-14 168 current->curr_ret_stack -= FTRACE_NOTRACE_DEPTH;
712406a6 Steven Rostedt 2009-02-09 169 barrier();
712406a6 Steven Rostedt 2009-02-09 170 current->ret_stack[index].ret = ret;
712406a6 Steven Rostedt 2009-02-09 171 current->ret_stack[index].func = func;
5d1a03dc Steven Rostedt 2009-03-23 172 current->ret_stack[index].calltime = calltime;
a2a16d6a Steven Rostedt 2009-03-24 @173 current->ret_stack[index].subtime = 0;
88e052f9 mmotm auto import 2016-10-04 174 #ifdef HAVE_FUNCTION_GRAPH_FP_TEST
71e308a2 Steven Rostedt 2009-06-18 175 current->ret_stack[index].fp = frame_pointer;
88e052f9 mmotm auto import 2016-10-04 176 #endif
:::::: The code at line 173 was first introduced by commit
:::::: a2a16d6a3156ef7309ca7328a20c35df9418e670 function-graph: add option to calculate graph time or not
:::::: TO: Steven Rostedt <srostedt@redhat.com>
:::::: CC: Steven Rostedt <srostedt@redhat.com>
---
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: 37778 bytes --]
next reply other threads:[~2016-10-04 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 23:35 kbuild test robot [this message]
2016-10-04 23:45 ` Andrew Morton
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=201610050750.gvhXrSoc%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.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