From: kernel test robot <lkp@intel.com>
To: Ben Levinsky <ben.levinsky@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev, git@amd.com,
Michal Simek <monstr@monstr.eu>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: [xilinx-xlnx:master 1071/1090] drivers/remoteproc/amd_mbv_bram_rproc.c:129:47: error: use of undeclared identifier 'dev_dbg'; did you mean 'cdev_del'?
Date: Wed, 07 Oct 2026 13:40:15 +0800 [thread overview]
Message-ID: <202610071345.F4lT1vwx-lkp@intel.com> (raw)
tree: https://github.com/Xilinx/linux-xlnx master
head: 235bd5e49f53bfea681cfd6c489ca1e0eab0b061
commit: dfff428d04b81b2cfd96007517cf9c85a38f427f [1071/1090] remoteproc: Add AMD MicroBlaze/V BRAM-based remote processor driver
config: sparc64-allmodconfig (https://download.01.org/0day-ci/archive/20261007/202610071345.F4lT1vwx-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261007/202610071345.F4lT1vwx-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/202610071345.F4lT1vwx-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/remoteproc/amd_mbv_bram_rproc.c:73:8: error: use of undeclared identifier 'rproc_mem_entry_ioremap_wc'; did you mean 'rproc_mem_entry_init'?
73 | rproc_mem_entry_ioremap_wc,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| rproc_mem_entry_init
include/linux/remoteproc.h:677:1: note: 'rproc_mem_entry_init' declared here
677 | rproc_mem_entry_init(struct device *dev,
| ^
drivers/remoteproc/amd_mbv_bram_rproc.c:74:8: error: use of undeclared identifier 'rproc_mem_entry_iounmap'; did you mean 'rproc_mem_entry_init'?
74 | rproc_mem_entry_iounmap,
| ^~~~~~~~~~~~~~~~~~~~~~~
| rproc_mem_entry_init
include/linux/remoteproc.h:677:1: note: 'rproc_mem_entry_init' declared here
677 | rproc_mem_entry_init(struct device *dev,
| ^
drivers/remoteproc/amd_mbv_bram_rproc.c:129:2: error: call to undeclared function 'rproc_elf_load_rsc_table_optional'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
129 | rproc_elf_load_rsc_table_optional(rproc, fw, dev_dbg,
| ^
drivers/remoteproc/amd_mbv_bram_rproc.c:129:2: note: did you mean 'rproc_elf_load_rsc_table'?
drivers/remoteproc/remoteproc_internal.h:117:5: note: 'rproc_elf_load_rsc_table' declared here
117 | int rproc_elf_load_rsc_table(struct rproc *rproc, const struct firmware *fw);
| ^
>> drivers/remoteproc/amd_mbv_bram_rproc.c:129:47: error: use of undeclared identifier 'dev_dbg'; did you mean 'cdev_del'?
129 | rproc_elf_load_rsc_table_optional(rproc, fw, dev_dbg,
| ^~~~~~~
| cdev_del
include/linux/cdev.h:35:6: note: 'cdev_del' declared here
35 | void cdev_del(struct cdev *);
| ^
4 errors generated.
vim +129 drivers/remoteproc/amd_mbv_bram_rproc.c
125
126 static int amd_bram_rproc_parse_fw(struct rproc *rproc,
127 const struct firmware *fw)
128 {
> 129 rproc_elf_load_rsc_table_optional(rproc, fw, dev_dbg,
130 "no resource table found\n");
131 return 0;
132 }
133
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-07 5:40 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=202610071345.F4lT1vwx-lkp@intel.com \
--to=lkp@intel.com \
--cc=ben.levinsky@amd.com \
--cc=git@amd.com \
--cc=llvm@lists.linux.dev \
--cc=mathieu.poirier@linaro.org \
--cc=monstr@monstr.eu \
--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.