From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [xlnx:master 173/199] include/linux/mtd/cfi.h:76:2: sparse: sparse: No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
Date: Wed, 11 Nov 2020 10:51:22 +0800 [thread overview]
Message-ID: <202011111012.2omzyBSc-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2904 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-arm-kernel(a)lists.infradead.org
TO: Nicholas Graumann <nick.graumann@gmail.com>
CC: Michal Simek <monstr@monstr.eu>
CC: Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>
tree: https://github.com/Xilinx/linux-xlnx master
head: 0a673209eb66ae657980dfab9ef90690647ee344
commit: 3e0fe58e108f56ee9ae5bd107aeb947ab18ef0a2 [173/199] spi: Move update_stripe definition to spi-mem
:::::: branch date: 10 months ago
:::::: commit date: 11 months ago
config: x86_64-randconfig-s022-20201110 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-76-gf680124b-dirty
# https://github.com/Xilinx/linux-xlnx/commit/3e0fe58e108f56ee9ae5bd107aeb947ab18ef0a2
git remote add xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xlnx master
git checkout 3e0fe58e108f56ee9ae5bd107aeb947ab18ef0a2
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
drivers/spi/spi-mem.c: note: in included file (through include/linux/mtd/spi-nor.h):
>> include/linux/mtd/cfi.h:76:2: sparse: sparse: No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
In file included from include/linux/mtd/spi-nor.h:14,
from drivers/spi/spi-mem.c:10:
include/linux/mtd/cfi.h:76:2: warning: #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work. [-Wcpp]
76 | #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
| ^~~~~~~
vim +76 include/linux/mtd/cfi.h
^1da177e4c3f415 Linus Torvalds 2005-04-16 74
241651d04d672fb David Woodhouse 2007-09-06 75 #ifndef cfi_interleave
241651d04d672fb David Woodhouse 2007-09-06 @76 #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
241651d04d672fb David Woodhouse 2007-09-06 77 static inline int cfi_interleave(void *cfi)
241651d04d672fb David Woodhouse 2007-09-06 78 {
241651d04d672fb David Woodhouse 2007-09-06 79 BUG();
241651d04d672fb David Woodhouse 2007-09-06 80 return 0;
241651d04d672fb David Woodhouse 2007-09-06 81 }
241651d04d672fb David Woodhouse 2007-09-06 82 #endif
241651d04d672fb David Woodhouse 2007-09-06 83
:::::: The code at line 76 was first introduced by commit
:::::: 241651d04d672fb685b2874707016cbbf95931e5 [MTD] Fix CFI build error when no map width or interleave supported
:::::: TO: David Woodhouse <dwmw2@infradead.org>
:::::: CC: David Woodhouse <dwmw2@infradead.org>
---
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: 29049 bytes --]
next reply other threads:[~2020-11-11 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 2:51 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-08 18:19 [xlnx:master 173/199] include/linux/mtd/cfi.h:76:2: sparse: sparse: No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work kernel test robot
2020-09-08 18:19 ` kernel test robot
2020-06-06 0:30 kernel test robot
2020-06-06 0:30 ` 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=202011111012.2omzyBSc-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@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.