From: kernel test robot <lkp@intel.com>
To: Rishabh Bhatnagar <rishabhb@codeaurora.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, bjorn.andersson@linaro.org,
tsoni@codeaurora.org, psodagud@codeaurora.org,
sidgup@codeaurora.org,
Rishabh Bhatnagar <rishabhb@codeaurora.org>
Subject: Re: [PATCH v2 1/3] soc: qcom: Add tracepoints to mdt loader
Date: Tue, 17 Nov 2020 10:14:35 +0800 [thread overview]
Message-ID: <202011171027.SMpqs92W-lkp@intel.com> (raw)
In-Reply-To: <1605563084-30385-2-git-send-email-rishabhb@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 4083 bytes --]
Hi Rishabh,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/perf/core]
[also build test WARNING on linux/master linus/master v5.10-rc4 next-20201116]
[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/Rishabh-Bhatnagar/Add-events-to-trace-remoteproc-lifecycle/20201117-054729
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 306e3e91edf1c6739a55312edd110d298ff498dd
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.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/437cc5c0ceb1f4b36564b99d7289af089576fdd0
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Rishabh-Bhatnagar/Add-events-to-trace-remoteproc-lifecycle/20201117-054729
git checkout 437cc5c0ceb1f4b36564b99d7289af089576fdd0
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
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 >>):
In file included from include/trace/define_trace.h:102,
from include/trace/events/mdt_loader.h:38,
from drivers/soc/qcom/mdt_loader.c:21:
include/trace/events/mdt_loader.h: In function 'trace_raw_output_qcom_mdt_load_segment':
>> include/trace/events/mdt_loader.h:33:12: warning: format '%p' expects argument of type 'void *', but argument 4 has type 'phys_addr_t' {aka 'unsigned int'} [-Wformat=]
33 | TP_printk("firmware:%s region start=%pa size=%zx",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/trace/trace_events.h:367:22: note: in definition of macro 'DECLARE_EVENT_CLASS'
367 | trace_seq_printf(s, print); \
| ^~~~~
include/trace/trace_events.h:80:9: note: in expansion of macro 'PARAMS'
80 | PARAMS(print)); \
| ^~~~~~
include/trace/events/mdt_loader.h:15:1: note: in expansion of macro 'TRACE_EVENT'
15 | TRACE_EVENT(qcom_mdt_load_segment,
| ^~~~~~~~~~~
include/trace/events/mdt_loader.h:33:2: note: in expansion of macro 'TP_printk'
33 | TP_printk("firmware:%s region start=%pa size=%zx",
| ^~~~~~~~~
In file included from include/trace/trace_events.h:401,
from include/trace/define_trace.h:102,
from include/trace/events/mdt_loader.h:38,
from drivers/soc/qcom/mdt_loader.c:21:
include/trace/events/mdt_loader.h:33:39: note: format string is defined here
33 | TP_printk("firmware:%s region start=%pa size=%zx",
| ~^
| |
| void *
| %d
vim +33 include/trace/events/mdt_loader.h
16
17 TP_PROTO(phys_addr_t region_start, size_t region_size, const char *fw),
18
19 TP_ARGS(region_start, region_size, fw),
20
21 TP_STRUCT__entry(
22 __field(phys_addr_t, region_start)
23 __field(size_t, region_size)
24 __string(fw, fw)
25 ),
26
27 TP_fast_assign(
28 __entry->region_start = region_start;
29 __entry->region_size = region_size;
30 __assign_str(fw, fw);
31 ),
32
> 33 TP_printk("firmware:%s region start=%pa size=%zx",
34 __get_str(fw), __entry->region_start, __entry->region_size)
35 );
36
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 76510 bytes --]
next prev parent reply other threads:[~2020-11-17 2:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 21:44 [PATCH v2 0/3] Add events to trace remoteproc lifecycle Rishabh Bhatnagar
2020-11-16 21:44 ` [PATCH v2 1/3] soc: qcom: Add tracepoints to mdt loader Rishabh Bhatnagar
2020-11-17 2:14 ` kernel test robot [this message]
2020-12-10 17:16 ` Bjorn Andersson
2020-11-16 21:44 ` [PATCH v2 2/3] firmware: scm: Add tracepoints to scm driver for pas calls Rishabh Bhatnagar
2020-12-10 17:12 ` Bjorn Andersson
2020-11-16 21:44 ` [PATCH v2 3/3] remoteproc: Add ftrace events to trace lifecycle of remoteprocs Rishabh Bhatnagar
2020-11-18 22:26 ` Mathieu Poirier
2020-12-10 18:17 ` Bjorn Andersson
2020-12-10 17:22 ` Bjorn Andersson
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=202011171027.SMpqs92W-lkp@intel.com \
--to=lkp@intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=psodagud@codeaurora.org \
--cc=rishabhb@codeaurora.org \
--cc=sidgup@codeaurora.org \
--cc=tsoni@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox