All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/2] remoteproc: imx_rproc: add elf memory hooks
Date: Wed, 29 Jul 2020 04:25:51 +0800	[thread overview]
Message-ID: <202007290405.Wp3NLmFa%lkp@intel.com> (raw)
In-Reply-To: <1595928673-26306-2-git-send-email-peng.fan@nxp.com>

[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]

Hi,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on soc/for-next]
[also build test WARNING on linus/master v5.8-rc7 next-20200728]
[cannot apply to xlnx/master remoteproc/for-next rpmsg/for-next]
[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/peng-fan-nxp-com/remoteproc-elf-support-platform-specific-memory-hook/20200728-173920
base:   https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git for-next
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-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
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64 

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 >>):

   drivers/remoteproc/imx_rproc.c: In function 'imx_rproc_memcpy':
>> drivers/remoteproc/imx_rproc.c:248:1: warning: no return statement in function returning non-void [-Wreturn-type]
     248 | }
         | ^
   drivers/remoteproc/imx_rproc.c: In function 'imx_rproc_memset':
   drivers/remoteproc/imx_rproc.c:253:1: warning: no return statement in function returning non-void [-Wreturn-type]
     253 | }
         | ^

vim +248 drivers/remoteproc/imx_rproc.c

   244	
   245	static void *imx_rproc_memcpy(struct rproc *rproc, void *dest, const void *src, size_t count)
   246	{
   247	       memcpy_toio((void * __iomem)dest, src, count);
 > 248	}
   249	

---
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: 73601 bytes --]

  reply	other threads:[~2020-07-28 20:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  9:31 [PATCH 1/2] remoteproc: elf: support platform specific memory hook peng.fan
2020-07-28  9:31 ` peng.fan
2020-07-28  9:31 ` [PATCH 2/2] remoteproc: imx_rproc: add elf memory hooks peng.fan
2020-07-28  9:31   ` peng.fan
2020-07-28 20:25   ` kernel test robot [this message]
2020-08-01  4:37   ` Oleksij Rempel
2020-08-01  4:37     ` Oleksij Rempel
2020-08-11 22:46   ` Mathieu Poirier
2020-08-11 22:46     ` Mathieu Poirier
2020-07-28 16:51 ` [PATCH 1/2] remoteproc: elf: support platform specific memory hook kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2020-07-28  9:29 peng.fan
2020-07-28  9:29 ` [PATCH 2/2] remoteproc: imx_rproc: add elf memory hooks peng.fan
2020-07-28  9:29   ` peng.fan

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=202007290405.Wp3NLmFa%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.