From: kernel test robot <lkp@intel.com>
To: Tudor Ambarus <tudor.ambarus@microchip.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [ambarus:spi-nor/next-id-collisions-v2 20/27] drivers/mtd/spi-nor/core.c:3126:6: warning: no previous prototype for 'spi_nor_set_mtd_info'
Date: Sun, 25 Jul 2021 04:11:57 +0800 [thread overview]
Message-ID: <202107250446.ZucQQ3Z0-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2482 bytes --]
tree: https://github.com/ambarus/linux-0day spi-nor/next-id-collisions-v2
head: b4bf25c4aeb0e9be35b688a2eaa4e9b902dff4f4
commit: 1db04a902d5710228c3172ac7113a78857a3695f [20/27] mtd: spi-nor: Introduce spi_nor_set_mtd_info()
config: sparc-randconfig-r024-20210724 (attached as .config)
compiler: sparc-linux-gcc (GCC) 10.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/ambarus/linux-0day/commit/1db04a902d5710228c3172ac7113a78857a3695f
git remote add ambarus https://github.com/ambarus/linux-0day
git fetch --no-tags ambarus spi-nor/next-id-collisions-v2
git checkout 1db04a902d5710228c3172ac7113a78857a3695f
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross ARCH=sparc
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/mtd/spi-nor/core.c:3126:6: warning: no previous prototype for 'spi_nor_set_mtd_info' [-Wmissing-prototypes]
3126 | void spi_nor_set_mtd_info(struct spi_nor *nor)
| ^~~~~~~~~~~~~~~~~~~~
vim +/spi_nor_set_mtd_info +3126 drivers/mtd/spi-nor/core.c
3125
> 3126 void spi_nor_set_mtd_info(struct spi_nor *nor)
3127 {
3128 struct mtd_info *mtd = &nor->mtd;
3129 struct device *dev = nor->dev;
3130
3131 spi_nor_register_locking_ops(nor);
3132
3133 /* Configure OTP parameters and ops */
3134 spi_nor_otp_init(nor);
3135
3136 mtd->dev.parent = dev;
3137 if (!mtd->name)
3138 mtd->name = dev_name(dev);
3139 mtd->priv = nor;
3140 mtd->type = MTD_NORFLASH;
3141 mtd->flags = MTD_CAP_NORFLASH;
3142 if (nor->info->flags & SPI_NOR_NO_ERASE)
3143 mtd->flags |= MTD_NO_ERASE;
3144 mtd->writesize = nor->params->writesize;
3145 mtd->writebufsize = nor->page_size;
3146 mtd->size = nor->params->size;
3147 mtd->_erase = spi_nor_erase;
3148 mtd->_read = spi_nor_read;
3149 mtd->_write = spi_nor_write;
3150 mtd->_suspend = spi_nor_suspend;
3151 mtd->_resume = spi_nor_resume;
3152 mtd->_get_device = spi_nor_get_device;
3153 mtd->_put_device = spi_nor_put_device;
3154 }
3155
---
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: 32498 bytes --]
reply other threads:[~2021-07-24 20:30 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=202107250446.ZucQQ3Z0-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tudor.ambarus@microchip.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).