From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ti:ti-rt-linux-5.4.y 3607/13037] drivers/remoteproc/remoteproc_core.c:1155:25: warning: cast between incompatible function types from 'int rproc struct fw_rsc_vendor int, int)' to 'int rproc void int, int, u16)' {aka 'int rproc void i...
Date: Fri, 08 Jan 2021 23:29:03 +0800 [thread overview]
Message-ID: <202101082357.dnF5n5ai-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3809 bytes --]
Hi Suman,
FYI, the error/warning still remains.
tree: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-rt-linux-5.4.y
head: cfa321c18ddfc08dc4f4417c93fe607dadd9cdee
commit: 6845d9cf8fce09da2bf37afcebd16ce022809cf9 [3607/13037] TEMP: remoteproc: Add support to handle device specific resource types
config: microblaze-randconfig-r025-20210108 (attached as .config)
compiler: microblaze-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
git remote add ti git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
git fetch --no-tags ti ti-rt-linux-5.4.y
git checkout 6845d9cf8fce09da2bf37afcebd16ce022809cf9
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=microblaze
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/remoteproc_core.c: In function 'rproc_find_carveout_by_name':
drivers/remoteproc/remoteproc_core.c:309:2: warning: function 'rproc_find_carveout_by_name' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
309 | vsnprintf(_name, sizeof(_name), name, args);
| ^~~~~~~~~
drivers/remoteproc/remoteproc_core.c: In function 'rproc_mem_entry_init':
drivers/remoteproc/remoteproc_core.c:1068:2: warning: function 'rproc_mem_entry_init' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
1068 | vsnprintf(mem->name, sizeof(mem->name), name, args);
| ^~~~~~~~~
drivers/remoteproc/remoteproc_core.c: In function 'rproc_of_resm_mem_entry_init':
drivers/remoteproc/remoteproc_core.c:1104:2: warning: function 'rproc_of_resm_mem_entry_init' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
1104 | vsnprintf(mem->name, sizeof(mem->name), name, args);
| ^~~~~~~~~
drivers/remoteproc/remoteproc_core.c: At top level:
>> drivers/remoteproc/remoteproc_core.c:1155:25: warning: cast between incompatible function types from 'int (*)(struct rproc *, struct fw_rsc_vendor *, int, int)' to 'int (*)(struct rproc *, void *, int, int, u16)' {aka 'int (*)(struct rproc *, void *, int, int, short unsigned int)'} [-Wcast-function-type]
1155 | [RSC_PRELOAD_VENDOR] = (rproc_handle_resource_t)rproc_handle_vendor_rsc,
| ^
drivers/remoteproc/remoteproc_core.c:1161:4: warning: cast between incompatible function types from 'int (*)(struct rproc *, struct fw_rsc_vendor *, int, int)' to 'int (*)(struct rproc *, void *, int, int, u16)' {aka 'int (*)(struct rproc *, void *, int, int, short unsigned int)'} [-Wcast-function-type]
1161 | (rproc_handle_resource_t)rproc_handle_vendor_rsc,
| ^
vim +1155 drivers/remoteproc/remoteproc_core.c
1146
1147 /*
1148 * A lookup table for resource handlers. The indices are defined in
1149 * enum fw_resource_type.
1150 */
1151 static rproc_handle_resource_t rproc_loading_handlers[RSC_LAST] = {
1152 [RSC_CARVEOUT] = (rproc_handle_resource_t)rproc_handle_carveout,
1153 [RSC_DEVMEM] = (rproc_handle_resource_t)rproc_handle_devmem,
1154 [RSC_TRACE] = (rproc_handle_resource_t)rproc_handle_trace,
> 1155 [RSC_PRELOAD_VENDOR] = (rproc_handle_resource_t)rproc_handle_vendor_rsc,
1156 [RSC_VDEV] = (rproc_handle_resource_t)rproc_handle_vdev,
1157 };
1158
---
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: 22016 bytes --]
reply other threads:[~2021-01-08 15:29 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=202101082357.dnF5n5ai-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.