From: kernel test robot <lkp@intel.com>
To: Frank Li <Frank.Li@nxp.com>,
vkoul@kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, imx@lists.linux.dev
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 2/2] dmaengine: fsl-edma: add trace event support
Date: Wed, 20 Sep 2023 05:47:07 +0800 [thread overview]
Message-ID: <202309200524.QTINjSsC-lkp@intel.com> (raw)
In-Reply-To: <20230919151430.2919042-3-Frank.Li@nxp.com>
Hi Frank,
kernel test robot noticed the following build warnings:
[auto build test WARNING on vkoul-dmaengine/next]
[also build test WARNING on linus/master v6.6-rc2 next-20230919]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Frank-Li/dmaengine-fsl-emda-add-debugfs-support/20230920-010257
base: https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git next
patch link: https://lore.kernel.org/r/20230919151430.2919042-3-Frank.Li%40nxp.com
patch subject: [PATCH v2 2/2] dmaengine: fsl-edma: add trace event support
config: arc-randconfig-001-20230920 (https://download.01.org/0day-ci/archive/20230920/202309200524.QTINjSsC-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230920/202309200524.QTINjSsC-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/202309200524.QTINjSsC-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/trace/define_trace.h:102,
from drivers/dma/fsl-edma-trace.h:134,
from drivers/dma/fsl-edma-common.h:238,
from drivers/dma/fsl-edma-trace.c:4:
drivers/dma/./fsl-edma-trace.h: In function 'trace_raw_output_edma_log_io':
>> drivers/dma/./fsl-edma-trace.h:28:19: warning: format '%lx' expects argument of type 'long unsigned int', but argument 3 has type 'int' [-Wformat=]
28 | TP_printk("offset %08lx: value %08x",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
include/trace/trace_events.h:203:34: note: in definition of macro 'DECLARE_EVENT_CLASS'
203 | trace_event_printf(iter, print); \
| ^~~~~
drivers/dma/./fsl-edma-trace.h:28:9: note: in expansion of macro 'TP_printk'
28 | TP_printk("offset %08lx: value %08x",
| ^~~~~~~~~
In file included from include/trace/trace_events.h:237:
drivers/dma/./fsl-edma-trace.h:28:31: note: format string is defined here
28 | TP_printk("offset %08lx: value %08x",
| ~~~~^
| |
| long unsigned int
| %08x
vim +28 drivers/dma/./fsl-edma-trace.h
14
15 DECLARE_EVENT_CLASS(edma_log_io,
16 TP_PROTO(struct fsl_edma_engine *edma, void __iomem *addr, u32 value),
17 TP_ARGS(edma, addr, value),
18 TP_STRUCT__entry(
19 __field(struct fsl_edma_engine *, edma)
20 __field(void __iomem *, addr)
21 __field(u32, value)
22 ),
23 TP_fast_assign(
24 __entry->edma = edma;
25 __entry->addr = addr;
26 __entry->value = value;
27 ),
> 28 TP_printk("offset %08lx: value %08x",
29 __entry->addr - __entry->edma->membase, __entry->value)
30 );
31
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-19 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 15:14 [PATCH v2 0/2] dmaengine: fsl_edma: add trace and debugfs support Frank Li
2023-09-19 15:14 ` [PATCH v2 1/2] dmaengine: fsl-emda: add " Frank Li
2023-09-19 23:51 ` kernel test robot
2023-09-20 21:45 ` kernel test robot
2023-09-19 15:14 ` [PATCH v2 2/2] dmaengine: fsl-edma: add trace event support Frank Li
2023-09-19 21:47 ` kernel test robot [this message]
2023-09-20 2:49 ` 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=202309200524.QTINjSsC-lkp@intel.com \
--to=lkp@intel.com \
--cc=Frank.Li@nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vkoul@kernel.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
Powered by JetHome