public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [mhiramat:topic/fprobe-event-ext 7/11] kernel/trace/trace_probe.c:647:9: error: incompatible pointer to integer conversion returning 'void *' from a function with result type 'int'
Date: Thu, 27 Jul 2023 07:26:15 +0800	[thread overview]
Message-ID: <202307270746.hoJf8GGv-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mhiramat/linux.git topic/fprobe-event-ext
head:   e4bb6f2230fbe828dad040af0befb139a5a5733b
commit: 33d45869bbad8c03d268d0634be77d860bbbc611 [7/11] tracing/probes: Support BTF field access from $retval
config: arm64-randconfig-r023-20230726 (https://download.01.org/0day-ci/archive/20230727/202307270746.hoJf8GGv-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20230727/202307270746.hoJf8GGv-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/202307270746.hoJf8GGv-lkp@intel.com/

All errors (new ones prefixed by >>):

>> kernel/trace/trace_probe.c:647:9: error: incompatible pointer to integer conversion returning 'void *' from a function with result type 'int' [-Wint-conversion]
     647 |         return ERR_PTR(-EOPNOTSUPP);
         |                ^~~~~~~~~~~~~~~~~~~~
   1 error generated.


vim +647 kernel/trace/trace_probe.c

b576e09701c7d0 Masami Hiramatsu (Google  2023-06-06  644) 
33d45869bbad8c Masami Hiramatsu (Google  2023-07-17  645) static int query_btf_context(struct traceprobe_parse_context *ctx)
18b1e870a49671 Masami Hiramatsu (Google  2023-06-06  646) {
18b1e870a49671 Masami Hiramatsu (Google  2023-06-06 @647) 	return ERR_PTR(-EOPNOTSUPP);
18b1e870a49671 Masami Hiramatsu (Google  2023-06-06  648) }
18b1e870a49671 Masami Hiramatsu (Google  2023-06-06  649) 

:::::: The code at line 647 was first introduced by commit
:::::: 18b1e870a49671745c31434b18bcfdd6f20cb6a1 tracing/probes: Add $arg* meta argument for all function args

:::::: TO: Masami Hiramatsu (Google) <mhiramat@kernel.org>
:::::: CC: Masami Hiramatsu (Google) <mhiramat@kernel.org>

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

                 reply	other threads:[~2023-07-26 23:27 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=202307270746.hoJf8GGv-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=mhiramat@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox