llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
* [trace:trace/urgent 3/6] kernel/trace/fgraph.c:282:15: error: conflicting types for 'ftrace_return_to_handler'
@ 2023-07-11  6:47 kernel test robot
  0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2023-07-11  6:47 UTC (permalink / raw)
  To: Arnd Bergmann; +Cc: llvm, oe-kbuild-all, Steven Rostedt (Google)

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace trace/urgent
head:   76ae40eccaa12b3b73256118ed3463dba523812d
commit: 8eebd18ffba37df7c5a78fdae9f9757b54795588 [3/6] tracing: arm64: Avoid missing-prototype warnings
config: i386-randconfig-i014-20230710 (https://download.01.org/0day-ci/archive/20230711/202307111442.GqM1Hsvm-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20230711/202307111442.GqM1Hsvm-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202307111442.GqM1Hsvm-lkp@intel.com/

All errors (new ones prefixed by >>):

>> kernel/trace/fgraph.c:282:15: error: conflicting types for 'ftrace_return_to_handler'
   unsigned long ftrace_return_to_handler(struct fgraph_ret_regs *ret_regs)
                 ^
   include/linux/ftrace.h:45:15: note: previous declaration is here
   unsigned long ftrace_return_to_handler(unsigned long frame_pointer);
                 ^
   1 error generated.


vim +/ftrace_return_to_handler +282 kernel/trace/fgraph.c

e73e679f656e67 Steven Rostedt (VMware  2018-11-15  276) 
a1be9ccc57f07d Donglin Peng            2023-04-08  277  /*
a1be9ccc57f07d Donglin Peng            2023-04-08  278   * After all architecures have selected HAVE_FUNCTION_GRAPH_RETVAL, we can
a1be9ccc57f07d Donglin Peng            2023-04-08  279   * leave only ftrace_return_to_handler(ret_regs).
a1be9ccc57f07d Donglin Peng            2023-04-08  280   */
a1be9ccc57f07d Donglin Peng            2023-04-08  281  #ifdef CONFIG_HAVE_FUNCTION_GRAPH_RETVAL
a1be9ccc57f07d Donglin Peng            2023-04-08 @282  unsigned long ftrace_return_to_handler(struct fgraph_ret_regs *ret_regs)
a1be9ccc57f07d Donglin Peng            2023-04-08  283  {
a1be9ccc57f07d Donglin Peng            2023-04-08  284  	return __ftrace_return_to_handler(ret_regs,
a1be9ccc57f07d Donglin Peng            2023-04-08  285  				fgraph_ret_regs_frame_pointer(ret_regs));
a1be9ccc57f07d Donglin Peng            2023-04-08  286  }
a1be9ccc57f07d Donglin Peng            2023-04-08  287  #else
a1be9ccc57f07d Donglin Peng            2023-04-08  288  unsigned long ftrace_return_to_handler(unsigned long frame_pointer)
a1be9ccc57f07d Donglin Peng            2023-04-08  289  {
a1be9ccc57f07d Donglin Peng            2023-04-08  290  	return __ftrace_return_to_handler(NULL, frame_pointer);
a1be9ccc57f07d Donglin Peng            2023-04-08  291  }
a1be9ccc57f07d Donglin Peng            2023-04-08  292  #endif
a1be9ccc57f07d Donglin Peng            2023-04-08  293  

:::::: The code at line 282 was first introduced by commit
:::::: a1be9ccc57f07d54278be34eed6bd679bc941c97 function_graph: Support recording and printing the return value of function

:::::: TO: Donglin Peng <pengdonglin@sangfor.com.cn>
:::::: CC: Steven Rostedt (Google) <rostedt@goodmis.org>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-07-11  6:47 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-11  6:47 [trace:trace/urgent 3/6] kernel/trace/fgraph.c:282:15: error: conflicting types for 'ftrace_return_to_handler' kernel test robot

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).