All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: peng.fan@oss.nxp.com, ohad@wizery.com,
	bjorn.andersson@linaro.org, mathieu.poirier@linaro.org,
	o.rempel@pengutronix.de, robh+dt@kernel.org,
	devicetree@vger.kernel.org
Cc: kbuild-all@lists.01.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, kernel@pengutronix.de,
	festevam@gmail.com
Subject: Re: [PATCH V12 07/10] remoteproc: imx_rproc: add i.MX specific parse fw hook
Date: Thu, 18 Feb 2021 23:07:35 +0800	[thread overview]
Message-ID: <202102182230.JAc1sfoX-lkp@intel.com> (raw)
In-Reply-To: <1613611500-12414-8-git-send-email-peng.fan@oss.nxp.com>

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

Hi,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on next-20210217]
[cannot apply to robh/for-next linus/master remoteproc/for-next rpmsg/for-next v5.11 v5.11-rc7 v5.11-rc6 v5.11]
[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-oss-nxp-com/remoteproc-imx_rproc-support-iMX8MQ-M/20210218-094227
base:    cd560d8023bf73c94d755908c8d4a0994dd1ec34
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
        # https://github.com/0day-ci/linux/commit/07b8942623e0ba5438d0574f1a3efa7c7a3d71cf
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review peng-fan-oss-nxp-com/remoteproc-imx_rproc-support-iMX8MQ-M/20210218-094227
        git checkout 07b8942623e0ba5438d0574f1a3efa7c7a3d71cf
        # 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>

Note: the linux-review/peng-fan-oss-nxp-com/remoteproc-imx_rproc-support-iMX8MQ-M/20210218-094227 HEAD 8634388851272efe3b40cfb88b0743639a3e3256 builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

   drivers/remoteproc/imx_rproc.c: In function 'imx_rproc_parse_fw':
>> drivers/remoteproc/imx_rproc.c:325:8: error: implicit declaration of function 'rproc_elf_load_rsc_table' [-Werror=implicit-function-declaration]
     325 |  ret = rproc_elf_load_rsc_table(rproc, fw);
         |        ^~~~~~~~~~~~~~~~~~~~~~~~
   drivers/remoteproc/imx_rproc.c: At top level:
>> drivers/remoteproc/imx_rproc.c:336:11: error: 'rproc_elf_load_segments' undeclared here (not in a function)
     336 |  .load  = rproc_elf_load_segments,
         |           ^~~~~~~~~~~~~~~~~~~~~~~
>> drivers/remoteproc/imx_rproc.c:338:27: error: 'rproc_elf_find_loaded_rsc_table' undeclared here (not in a function)
     338 |  .find_loaded_rsc_table = rproc_elf_find_loaded_rsc_table,
         |                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/remoteproc/imx_rproc.c:339:18: error: 'rproc_elf_sanity_check' undeclared here (not in a function)
     339 |  .sanity_check = rproc_elf_sanity_check,
         |                  ^~~~~~~~~~~~~~~~~~~~~~
>> drivers/remoteproc/imx_rproc.c:340:19: error: 'rproc_elf_get_boot_addr' undeclared here (not in a function)
     340 |  .get_boot_addr = rproc_elf_get_boot_addr,
         |                   ^~~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/rproc_elf_load_rsc_table +325 drivers/remoteproc/imx_rproc.c

   317	
   318	static int imx_rproc_parse_fw(struct rproc *rproc, const struct firmware *fw)
   319	{
   320		int ret = imx_rproc_parse_memory_regions(rproc);
   321	
   322		if (ret)
   323			return ret;
   324	
 > 325		ret = rproc_elf_load_rsc_table(rproc, fw);
   326		if (ret)
   327			dev_info(&rproc->dev, "No resource table in elf\n");
   328	
   329		return 0;
   330	}
   331	
   332	static const struct rproc_ops imx_rproc_ops = {
   333		.start		= imx_rproc_start,
   334		.stop		= imx_rproc_stop,
   335		.da_to_va       = imx_rproc_da_to_va,
 > 336		.load		= rproc_elf_load_segments,
   337		.parse_fw	= imx_rproc_parse_fw,
 > 338		.find_loaded_rsc_table = rproc_elf_find_loaded_rsc_table,
 > 339		.sanity_check	= rproc_elf_sanity_check,
 > 340		.get_boot_addr	= rproc_elf_get_boot_addr,
   341	};
   342	

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

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH V12 07/10] remoteproc: imx_rproc: add i.MX specific parse fw hook
Date: Thu, 18 Feb 2021 23:07:35 +0800	[thread overview]
Message-ID: <202102182230.JAc1sfoX-lkp@intel.com> (raw)
In-Reply-To: <1613611500-12414-8-git-send-email-peng.fan@oss.nxp.com>

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

Hi,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on next-20210217]
[cannot apply to robh/for-next linus/master remoteproc/for-next rpmsg/for-next v5.11 v5.11-rc7 v5.11-rc6 v5.11]
[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-oss-nxp-com/remoteproc-imx_rproc-support-iMX8MQ-M/20210218-094227
base:    cd560d8023bf73c94d755908c8d4a0994dd1ec34
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
        # https://github.com/0day-ci/linux/commit/07b8942623e0ba5438d0574f1a3efa7c7a3d71cf
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review peng-fan-oss-nxp-com/remoteproc-imx_rproc-support-iMX8MQ-M/20210218-094227
        git checkout 07b8942623e0ba5438d0574f1a3efa7c7a3d71cf
        # 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>

Note: the linux-review/peng-fan-oss-nxp-com/remoteproc-imx_rproc-support-iMX8MQ-M/20210218-094227 HEAD 8634388851272efe3b40cfb88b0743639a3e3256 builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

   drivers/remoteproc/imx_rproc.c: In function 'imx_rproc_parse_fw':
>> drivers/remoteproc/imx_rproc.c:325:8: error: implicit declaration of function 'rproc_elf_load_rsc_table' [-Werror=implicit-function-declaration]
     325 |  ret = rproc_elf_load_rsc_table(rproc, fw);
         |        ^~~~~~~~~~~~~~~~~~~~~~~~
   drivers/remoteproc/imx_rproc.c: At top level:
>> drivers/remoteproc/imx_rproc.c:336:11: error: 'rproc_elf_load_segments' undeclared here (not in a function)
     336 |  .load  = rproc_elf_load_segments,
         |           ^~~~~~~~~~~~~~~~~~~~~~~
>> drivers/remoteproc/imx_rproc.c:338:27: error: 'rproc_elf_find_loaded_rsc_table' undeclared here (not in a function)
     338 |  .find_loaded_rsc_table = rproc_elf_find_loaded_rsc_table,
         |                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/remoteproc/imx_rproc.c:339:18: error: 'rproc_elf_sanity_check' undeclared here (not in a function)
     339 |  .sanity_check = rproc_elf_sanity_check,
         |                  ^~~~~~~~~~~~~~~~~~~~~~
>> drivers/remoteproc/imx_rproc.c:340:19: error: 'rproc_elf_get_boot_addr' undeclared here (not in a function)
     340 |  .get_boot_addr = rproc_elf_get_boot_addr,
         |                   ^~~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/rproc_elf_load_rsc_table +325 drivers/remoteproc/imx_rproc.c

   317	
   318	static int imx_rproc_parse_fw(struct rproc *rproc, const struct firmware *fw)
   319	{
   320		int ret = imx_rproc_parse_memory_regions(rproc);
   321	
   322		if (ret)
   323			return ret;
   324	
 > 325		ret = rproc_elf_load_rsc_table(rproc, fw);
   326		if (ret)
   327			dev_info(&rproc->dev, "No resource table in elf\n");
   328	
   329		return 0;
   330	}
   331	
   332	static const struct rproc_ops imx_rproc_ops = {
   333		.start		= imx_rproc_start,
   334		.stop		= imx_rproc_stop,
   335		.da_to_va       = imx_rproc_da_to_va,
 > 336		.load		= rproc_elf_load_segments,
   337		.parse_fw	= imx_rproc_parse_fw,
 > 338		.find_loaded_rsc_table = rproc_elf_find_loaded_rsc_table,
 > 339		.sanity_check	= rproc_elf_sanity_check,
 > 340		.get_boot_addr	= rproc_elf_get_boot_addr,
   341	};
   342	

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

  reply	other threads:[~2021-02-18 15:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18  1:24 [PATCH V12 00/10] remoteproc: imx_rproc: support iMX8MQ/M peng.fan
2021-02-18  1:24 ` peng.fan
2021-02-18  1:24 ` [PATCH V12 01/10] dt-bindings: remoteproc: convert imx rproc bindings to json-schema peng.fan
2021-02-18  1:24   ` peng.fan
2021-03-03  6:53   ` Peng Fan (OSS)
2021-03-03  6:53     ` Peng Fan (OSS)
2021-03-05 22:36     ` Rob Herring
2021-03-05 22:36       ` Rob Herring
2021-03-05 22:37   ` Rob Herring
2021-03-05 22:37     ` Rob Herring
2021-02-18  1:24 ` [PATCH V12 02/10] dt-bindings: remoteproc: imx_rproc: add i.MX8MQ/M support peng.fan
2021-02-18  1:24   ` peng.fan
2021-03-05 22:39   ` Rob Herring
2021-03-05 22:39     ` Rob Herring
2021-02-18  1:24 ` [PATCH V12 03/10] remoteproc: introduce is_iomem to rproc_mem_entry peng.fan
2021-02-18  1:24   ` peng.fan
2021-02-18  1:24 ` [PATCH V12 04/10] remoteproc: add is_iomem to da_to_va peng.fan
2021-02-18  1:24   ` peng.fan
2021-02-18  3:21   ` kernel test robot
2021-02-18  3:21     ` kernel test robot
2021-02-18  1:24 ` [PATCH V12 05/10] remoteproc: imx_rproc: correct err message peng.fan
2021-02-18  1:24   ` peng.fan
2021-02-18  1:24 ` [PATCH V12 06/10] remoteproc: imx_rproc: use devm_ioremap peng.fan
2021-02-18  1:24   ` peng.fan
2021-02-18  1:24 ` [PATCH V12 07/10] remoteproc: imx_rproc: add i.MX specific parse fw hook peng.fan
2021-02-18  1:24   ` peng.fan
2021-02-18 15:07   ` kernel test robot [this message]
2021-02-18 15:07     ` kernel test robot
2021-02-18  1:24 ` [PATCH V12 08/10] remoteproc: imx_rproc: support i.MX8MQ/M peng.fan
2021-02-18  1:24   ` peng.fan
2021-02-18  1:24 ` [PATCH V12 09/10] remoteproc: imx_rproc: ignore mapping vdev regions peng.fan
2021-02-18  1:24   ` peng.fan
2021-02-18  1:25 ` [PATCH V12 10/10] remoteproc: imx_proc: enable virtio/mailbox peng.fan
2021-02-18  1:25   ` 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=202102182230.JAc1sfoX-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kernel@pengutronix.de \
    --cc=mathieu.poirier@linaro.org \
    --cc=o.rempel@pengutronix.de \
    --cc=ohad@wizery.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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 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.