From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [stffrdhrn:litex-gpio-fix 15/26] drivers/mtd/spi-nor/litex-spiflash.c:305:15: error: initialization of 'int (*)(struct spi_nor *, u8, const u8 *, size_t)' {aka 'int (*)(struct spi_nor *, unsigned char, const unsigned char *, long unsigned int)'} from incompatible pointer type 'ssize_t ...
Date: Thu, 29 Apr 2021 18:00:48 +0800 [thread overview]
Message-ID: <202104291845.WRtyUOn6-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3071 bytes --]
tree: https://github.com/stffrdhrn/linux.git litex-gpio-fix
head: 6f903ad53b35652c15f91265053f437a6b6f17f0
commit: 85b04bca0da9f332aff3820373b7169644d7332b [15/26] LiteX: driver for SPI Flash (mtd) device
config: ia64-allmodconfig (attached as .config)
compiler: ia64-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/stffrdhrn/linux/commit/85b04bca0da9f332aff3820373b7169644d7332b
git remote add stffrdhrn https://github.com/stffrdhrn/linux.git
git fetch --no-tags stffrdhrn litex-gpio-fix
git checkout 85b04bca0da9f332aff3820373b7169644d7332b
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=ia64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/mtd/spi-nor/litex-spiflash.c: In function 'cs':
drivers/mtd/spi-nor/litex-spiflash.c:71:20: error: implicit declaration of function 'litex_get_reg'; did you mean '_litex_get_reg'? [-Werror=implicit-function-declaration]
71 | u8 curr_val = (u8)litex_get_reg(spi->base + SPIFLASH_BITBANG_OFFSET, SPIFLASH_BITBANG_SIZE);
| ^~~~~~~~~~~~~
| _litex_get_reg
drivers/mtd/spi-nor/litex-spiflash.c:75:2: error: implicit declaration of function 'litex_set_reg'; did you mean '_litex_set_reg'? [-Werror=implicit-function-declaration]
75 | litex_set_reg(spi->base + SPIFLASH_BITBANG_OFFSET, SPIFLASH_BITBANG_SIZE, set_val);
| ^~~~~~~~~~~~~
| _litex_set_reg
drivers/mtd/spi-nor/litex-spiflash.c: At top level:
>> drivers/mtd/spi-nor/litex-spiflash.c:305:15: error: initialization of 'int (*)(struct spi_nor *, u8, const u8 *, size_t)' {aka 'int (*)(struct spi_nor *, unsigned char, const unsigned char *, long unsigned int)'} from incompatible pointer type 'ssize_t (*)(struct spi_nor *, u8, const u8 *, size_t)' {aka 'long int (*)(struct spi_nor *, unsigned char, const unsigned char *, long unsigned int)'} [-Werror=incompatible-pointer-types]
305 | .write_reg = spi_flash_nor_write_reg,
| ^~~~~~~~~~~~~~~~~~~~~~~
drivers/mtd/spi-nor/litex-spiflash.c:305:15: note: (near initialization for 'litex_spi_controller_ops.write_reg')
cc1: some warnings being treated as errors
vim +305 drivers/mtd/spi-nor/litex-spiflash.c
300
301 static const struct spi_nor_controller_ops litex_spi_controller_ops = {
302 .read = spi_flash_nor_read,
303 .write = spi_flash_nor_write,
304 .read_reg = spi_flash_nor_read_reg,
> 305 .write_reg = spi_flash_nor_write_reg,
306 .erase = spi_flash_nor_erase,
307 };
308
---
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: 63857 bytes --]
next reply other threads:[~2021-04-29 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 10:00 kernel test robot [this message]
2021-04-29 21:54 [stffrdhrn:litex-gpio-fix 15/26] drivers/mtd/spi-nor/litex-spiflash.c:305:15: error: initialization of 'int (*)(struct spi_nor *, u8, const u8 *, size_t)' {aka 'int (*)(struct spi_nor *, unsigned char, const unsigned char *, long unsigned int)'} from incompatible pointer type 'ssize_t kernel test robot
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=202104291845.WRtyUOn6-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.