From: Mark Rutland <mark.rutland@arm.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [mark:arm64/ftrace/per-callsite-ops 4/8] kernel/trace/ftrace.c:2505:1: error: conflicting types for 'ftrace_find_unique_ops'; have 'struct ftrace_ops *(struct dyn_ftrace *)'
Date: Tue, 10 Jan 2023 16:32:39 +0000 [thread overview]
Message-ID: <Y72TJ3qQuvx3gIOi@FVFF77S0Q05N> (raw)
In-Reply-To: <202301100944.E0mV3kSO-lkp@intel.com>
On Tue, Jan 10, 2023 at 09:04:40AM +0800, kernel test robot wrote:
> Hi Mark,
>
> FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git arm64/ftrace/per-callsite-ops
> head: 8f064db83949d4f90fccbda17ef5980695c789df
> commit: f589df82765a8a167c3ee4385fe2490c934f491f [4/8] ftrace: Add DYNAMIC_FTRACE_WITH_CALL_OPS
> config: x86_64-rhel-8.3-func
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/commit/?id=f589df82765a8a167c3ee4385fe2490c934f491f
> git remote add mark https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git
> git fetch --no-tags mark arm64/ftrace/per-callsite-ops
> git checkout f589df82765a8a167c3ee4385fe2490c934f491f
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> make W=1 O=build_dir ARCH=x86_64 olddefconfig
> make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> In file included from kernel/trace/ftrace.c:29:
> include/linux/ftrace.h:62:50: warning: 'struct dyn_ftrace' declared inside parameter list will not be visible outside of this definition or declaration
> 62 | struct ftrace_ops *ftrace_find_unique_ops(struct dyn_ftrace *rec);
> | ^~~~~~~~~~
I think this is the fundamental issue here, since the below two cases:
> >> kernel/trace/ftrace.c:2505:1: error: conflicting types for 'ftrace_find_unique_ops'; have 'struct ftrace_ops *(struct dyn_ftrace *)'
> 2505 | ftrace_find_unique_ops(struct dyn_ftrace *rec)
> | ^~~~~~~~~~~~~~~~~~~~~~
> In file included from kernel/trace/ftrace.c:29:
> include/linux/ftrace.h:62:20: note: previous declaration of 'ftrace_find_unique_ops' with type 'struct ftrace_ops *(struct dyn_ftrace *)'
> 62 | struct ftrace_ops *ftrace_find_unique_ops(struct dyn_ftrace *rec);
> | ^~~~~~~~~~~~~~~~~~~~~~
... look identical.
I'll move the definition up earlier in <linux/ftrace.h>
Thanks,
Mark.
prev parent reply other threads:[~2023-01-10 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 1:04 [mark:arm64/ftrace/per-callsite-ops 4/8] kernel/trace/ftrace.c:2505:1: error: conflicting types for 'ftrace_find_unique_ops'; have 'struct ftrace_ops *(struct dyn_ftrace *)' kernel test robot
2023-01-10 16:32 ` Mark Rutland [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=Y72TJ3qQuvx3gIOi@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.