From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [android-common:android13-5.15-lts 2/2] include/linux/mtd/cfi.h:62:2: sparse: sparse: No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
Date: Sun, 25 Oct 2026 18:45:05 +0100 [thread overview]
Message-ID: <202610251809.pyVaizvw-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check first_new_problem: include/linux/mtd/cfi.h:62:2: sparse: sparse: No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work."
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: cros-kernel-buildreports@googlegroups.com
tree: https://android.googlesource.com/kernel/common android13-5.15-lts
head: 28ca5d8b733ed5c4ea847e57cc94f90cfa929e94
commit: ccb03ec4294c0bab21252e69789c80cd766eec1e [2/2] spi: bcm-qspi: fix SFDP BFPT read by usig mspi read
:::::: branch date: 7 hours ago
:::::: commit date: 2 years, 8 months ago
config: arm-randconfig-r2300-20261025 (https://download.01.org/0day-ci/archive/20261025/202610251809.pyVaizvw-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project a808f8ea7fdc61ead417bfe55e8ef5f728776aeb)
sparse: v0.6.5-rc1-1-gc4640450
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261025/202610251809.pyVaizvw-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202610251809.pyVaizvw-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/spi/spi-bcm-qspi.c: note: in included file (through include/linux/mtd/spi-nor.h):
>> include/linux/mtd/cfi.h:62:2: sparse: sparse: No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
drivers/spi/spi-bcm-qspi.c:363:30: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [assigned] [usertype] data @@ got restricted __le32 [usertype] @@
drivers/spi/spi-bcm-qspi.c:363:30: sparse: expected unsigned int [assigned] [usertype] data
drivers/spi/spi-bcm-qspi.c:363:30: sparse: got restricted __le32 [usertype]
drivers/spi/spi-bcm-qspi.c:327:24: sparse: sparse: cast to restricted __le32
vim +62 include/linux/mtd/cfi.h
^1da177e4c3f41 Linus Torvalds 2005-04-16 60
241651d04d672f David Woodhouse 2007-09-06 61 #ifndef cfi_interleave
241651d04d672f David Woodhouse 2007-09-06 @62 #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
241651d04d672f David Woodhouse 2007-09-06 63 static inline int cfi_interleave(void *cfi)
241651d04d672f David Woodhouse 2007-09-06 64 {
241651d04d672f David Woodhouse 2007-09-06 65 BUG();
241651d04d672f David Woodhouse 2007-09-06 66 return 0;
241651d04d672f David Woodhouse 2007-09-06 67 }
241651d04d672f David Woodhouse 2007-09-06 68 #endif
241651d04d672f David Woodhouse 2007-09-06 69
:::::: The code at line 62 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
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-25 17:45 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=202610251809.pyVaizvw-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.