From: kernel test robot <lkp@intel.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jolsa-perf:test 4/10] include/linux/ftrace.h:569:5: warning: no previous prototype for 'modify_ftrace_direct_hash'
Date: Wed, 24 Sep 2025 11:10:05 +0800 [thread overview]
Message-ID: <202509241138.BhVTtAhI-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git test
head: 1b7fc74c36a93e90816f58c37a84522f0949095a
commit: bbc3f1e07924e420b74b4bf49f1c3b0a924db927 [4/10] ftrace: Add modify_ftrace_direct_hash function
config: alpha-randconfig-r073-20250924 (https://download.01.org/0day-ci/archive/20250924/202509241138.BhVTtAhI-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250924/202509241138.BhVTtAhI-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/202509241138.BhVTtAhI-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/perf_event.h:43,
from include/linux/trace_events.h:10,
from include/trace/syscall.h:7,
from include/linux/syscalls.h:95,
from init/main.c:22:
include/linux/ftrace.h:559:5: warning: no previous prototype for 'register_ftrace_direct_hash' [-Wmissing-prototypes]
int register_ftrace_direct_hash(struct ftrace_ops *ops, struct ftrace_hash *hash)
^~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/ftrace.h:564:5: warning: no previous prototype for 'unregister_ftrace_direct_hash' [-Wmissing-prototypes]
int unregister_ftrace_direct_hash(struct ftrace_ops *ops, struct ftrace_hash *hash)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/ftrace.h:569:5: warning: no previous prototype for 'modify_ftrace_direct_hash' [-Wmissing-prototypes]
int modify_ftrace_direct_hash(struct ftrace_ops *ops, struct ftrace_hash *hash, bool do_direct_lock)
^~~~~~~~~~~~~~~~~~~~~~~~~
vim +/modify_ftrace_direct_hash +569 include/linux/ftrace.h
558
> 559 int register_ftrace_direct_hash(struct ftrace_ops *ops, struct ftrace_hash *hash)
560 {
561 return -ENODEV;
562 }
563
564 int unregister_ftrace_direct_hash(struct ftrace_ops *ops, struct ftrace_hash *hash)
565 {
566 return -ENODEV;
567 }
568
> 569 int modify_ftrace_direct_hash(struct ftrace_ops *ops, struct ftrace_hash *hash, bool do_direct_lock)
570 {
571 return -ENODEV;
572 }
573
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-09-24 3:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202509241138.BhVTtAhI-lkp@intel.com \
--to=lkp@intel.com \
--cc=jolsa@kernel.org \
--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.