* [ti:ti-rt-linux-5.10.y 10024/10213] drivers/remoteproc/ti_k3_m4_remoteproc.c:327:13: warning: variable 'boot_addr' set but not used
@ 2021-12-08 16:45 kernel test robot
0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2021-12-08 16:45 UTC (permalink / raw)
To: kbuild-all
[-- Attachment #1: Type: text/plain, Size: 2652 bytes --]
tree: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-rt-linux-5.10.y
head: 541ec9a6995c3dd881d6f0b63cc714a08ded457d
commit: 821f316d0ad8840a5bb6563b5461dce9289fd558 [10024/10213] remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20211209/202112090056.3GhFxDhB-lkp(a)intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.2.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
git remote add ti git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
git fetch --no-tags ti ti-rt-linux-5.10.y
git checkout 821f316d0ad8840a5bb6563b5461dce9289fd558
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/net/ethernet/ti/ drivers/remoteproc/
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/ti_k3_m4_remoteproc.c: In function 'k3_m4_rproc_start':
>> drivers/remoteproc/ti_k3_m4_remoteproc.c:327:13: warning: variable 'boot_addr' set but not used [-Wunused-but-set-variable]
327 | u32 boot_addr;
| ^~~~~~~~~
vim +/boot_addr +327 drivers/remoteproc/ti_k3_m4_remoteproc.c
315
316 /*
317 * Power up the M4F remote processor.
318 *
319 * This function will be invoked only after the firmware for this rproc
320 * was loaded, parsed successfully, and all of its resource requirements
321 * were met.
322 */
323 static int k3_m4_rproc_start(struct rproc *rproc)
324 {
325 struct k3_m4_rproc *kproc = rproc->priv;
326 struct device *dev = kproc->dev;
> 327 u32 boot_addr;
328 int ret;
329
330 if (kproc->ipc_only) {
331 dev_err(dev, "%s cannot be invoked in IPC-only mode\n",
332 __func__);
333 return -EINVAL;
334 }
335
336 ret = k3_m4_rproc_request_mbox(rproc);
337 if (ret)
338 return ret;
339
340 boot_addr = rproc->bootaddr;
341 ret = k3_m4_rproc_release(kproc);
342 if (ret)
343 goto put_mbox;
344
345 return 0;
346
347 put_mbox:
348 mbox_free_channel(kproc->mbox);
349 return ret;
350 }
351
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-12-08 16:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-08 16:45 [ti:ti-rt-linux-5.10.y 10024/10213] drivers/remoteproc/ti_k3_m4_remoteproc.c:327:13: warning: variable 'boot_addr' set but not used kernel test robot
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.