All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev, mhi@lists.linux.dev
Subject: [mani-mhi:mhi-next 13/15] drivers/bus/mhi/ep/main.c:520:17: warning: format specifies type 'long' but the argument has type 'size_t' (aka 'unsigned int')
Date: Fri, 15 Dec 2023 04:18:09 +0800	[thread overview]
Message-ID: <202312150418.TOQGiuVw-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mani/mhi.git mhi-next
head:   f5668f251e29292326e45a022f933c15740a8af2
commit: e59bba2cc6c746942c7c2d83ebcd9b92ae0a1aca [13/15] bus: mhi: ep: Add support for async DMA write operation
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20231215/202312150418.TOQGiuVw-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231215/202312150418.TOQGiuVw-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/202312150418.TOQGiuVw-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/bus/mhi/ep/main.c:520:17: warning: format specifies type 'long' but the argument has type 'size_t' (aka 'unsigned int') [-Wformat]
   ring->er_index, ring->rd_offset);
                   ^~~~~~~~~~~~~~~
   include/linux/dev_printk.h:155:39: note: expanded from macro 'dev_dbg'
           dynamic_dev_dbg(dev, dev_fmt(fmt), ##__VA_ARGS__)
                                        ~~~     ^~~~~~~~~~~
   include/linux/dynamic_debug.h:274:19: note: expanded from macro 'dynamic_dev_dbg'
                              dev, fmt, ##__VA_ARGS__)
                                   ~~~    ^~~~~~~~~~~
   include/linux/dynamic_debug.h:250:59: note: expanded from macro '_dynamic_func_call'
           _dynamic_func_call_cls(_DPRINTK_CLASS_DFLT, fmt, func, ##__VA_ARGS__)
                                                                    ^~~~~~~~~~~
   include/linux/dynamic_debug.h:248:65: note: expanded from macro '_dynamic_func_call_cls'
           __dynamic_func_call_cls(__UNIQUE_ID(ddebug), cls, fmt, func, ##__VA_ARGS__)
                                                                          ^~~~~~~~~~~
   include/linux/dynamic_debug.h:224:15: note: expanded from macro '__dynamic_func_call_cls'
                   func(&id, ##__VA_ARGS__);                       \
                               ^~~~~~~~~~~
   drivers/bus/mhi/ep/main.c:601:1: warning: format specifies type 'long' but the argument has type 'size_t' (aka 'unsigned int') [-Wformat]
   mhi_chan->rd_offset);
   ^~~~~~~~~~~~~~~~~~~
   include/linux/dev_printk.h:155:39: note: expanded from macro 'dev_dbg'
           dynamic_dev_dbg(dev, dev_fmt(fmt), ##__VA_ARGS__)
                                        ~~~     ^~~~~~~~~~~
   include/linux/dynamic_debug.h:274:19: note: expanded from macro 'dynamic_dev_dbg'
                              dev, fmt, ##__VA_ARGS__)
                                   ~~~    ^~~~~~~~~~~
   include/linux/dynamic_debug.h:250:59: note: expanded from macro '_dynamic_func_call'
           _dynamic_func_call_cls(_DPRINTK_CLASS_DFLT, fmt, func, ##__VA_ARGS__)
                                                                    ^~~~~~~~~~~
   include/linux/dynamic_debug.h:248:65: note: expanded from macro '_dynamic_func_call_cls'
           __dynamic_func_call_cls(__UNIQUE_ID(ddebug), cls, fmt, func, ##__VA_ARGS__)
                                                                          ^~~~~~~~~~~
   include/linux/dynamic_debug.h:224:15: note: expanded from macro '__dynamic_func_call_cls'
                   func(&id, ##__VA_ARGS__);                       \
                               ^~~~~~~~~~~
   2 warnings generated.


vim +520 drivers/bus/mhi/ep/main.c

   499	
   500	static void mhi_ep_skb_completion(struct mhi_ep_buf_info *buf_info)
   501	{
   502		struct mhi_ep_device *mhi_dev = buf_info->mhi_dev;
   503		struct mhi_ep_cntrl *mhi_cntrl = mhi_dev->mhi_cntrl;
   504		struct mhi_ep_chan *mhi_chan = mhi_dev->dl_chan;
   505		struct mhi_ep_ring *ring = &mhi_cntrl->mhi_chan[mhi_chan->chan].ring;
   506		struct mhi_ring_element *el = &ring->ring_cache[ring->rd_offset];
   507		struct device *dev = &mhi_dev->dev;
   508		struct mhi_result result = {};
   509		int ret;
   510	
   511		if (mhi_chan->xfer_cb) {
   512			result.buf_addr = buf_info->cb_buf;
   513			result.dir = mhi_chan->dir;
   514			result.bytes_xferd = buf_info->size;
   515	
   516			mhi_chan->xfer_cb(mhi_dev, &result);
   517		}
   518	
   519		dev_dbg(dev, "Sending completion for ring (%d) rd_offset: %ld\n",
 > 520	ring->er_index, ring->rd_offset);
   521		ret = mhi_ep_send_completion_event(mhi_cntrl, ring, el, buf_info->size,
   522						   buf_info->code);
   523		if (ret) {
   524			dev_err(dev, "Error sending transfer completion event\n");
   525			return;
   526		}
   527	
   528		mhi_ep_ring_inc_index(ring);
   529	}
   530	

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

                 reply	other threads:[~2023-12-14 20:18 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=202312150418.TOQGiuVw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mhi@lists.linux.dev \
    --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.