From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2] [RFC] trace: Add kprobe on tracepoint
Date: Tue, 10 Aug 2021 22:54:37 +0800 [thread overview]
Message-ID: <202108102249.HX31986j-lkp@intel.com> (raw)
In-Reply-To: <20210810112108.1663174-1-tz.stoyanov@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2388 bytes --]
Hi "Tzvetomir,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on v5.14-rc5]
[also build test WARNING on next-20210810]
[cannot apply to tip/perf/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Tzvetomir-Stoyanov-VMware/trace-Add-kprobe-on-tracepoint/20210810-192225
base: 36a21d51725af2ce0700c6ebcb6b9594aac658a6
config: hexagon-randconfig-r041-20210810 (attached as .config)
compiler: clang version 12.0.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/e3bec14eb58da9408eba8ccc55c9f5cf4e1ff114
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Tzvetomir-Stoyanov-VMware/trace-Add-kprobe-on-tracepoint/20210810-192225
git checkout e3bec14eb58da9408eba8ccc55c9f5cf4e1ff114
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=hexagon
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> kernel/trace/trace_eprobe.c:46:6: warning: no previous prototype for function 'trace_event_probe_cleanup' [-Wmissing-prototypes]
void trace_event_probe_cleanup(struct trace_eprobe *ep)
^
kernel/trace/trace_eprobe.c:46:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void trace_event_probe_cleanup(struct trace_eprobe *ep)
^
static
1 warning generated.
vim +/trace_event_probe_cleanup +46 kernel/trace/trace_eprobe.c
45
> 46 void trace_event_probe_cleanup(struct trace_eprobe *ep)
47 {
48 trace_probe_cleanup(&ep->tp);
49 kfree(ep->event_name);
50 kfree(ep->event_system);
51 if (ep->event)
52 module_put(ep->event->mod);
53 kfree(ep);
54 }
55
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 25181 bytes --]
next prev parent reply other threads:[~2021-08-10 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 11:21 [PATCH v2] [RFC] trace: Add kprobe on tracepoint Tzvetomir Stoyanov (VMware)
2021-08-10 14:51 ` kernel test robot
2021-08-10 14:54 ` kernel test robot [this message]
2021-08-10 15:05 ` kernel test robot
2021-08-10 15:59 ` kernel test robot
2021-08-10 15:59 ` [RFC PATCH] trace: trace_event_probe_cleanup() can be static kernel test robot
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=202108102249.HX31986j-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.