From: kernel test robot <lkp@intel.com>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-arm-kernel@lists.infradead.org,
Michal Simek <monstr@monstr.eu>,
Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>
Subject: [xilinx-xlnx:xlnx_rebase_v5.10 1403/1972] include/linux/mtd/cfi.h:62:2: warning: No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
Date: Tue, 5 Oct 2021 15:30:49 +0800 [thread overview]
Message-ID: <202110051540.hVkTkh04-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2950 bytes --]
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v5.10
head: 47ec4129b04ae9b0e061323088cfc7196b62e373
commit: 0ee2a65f834c5d35ad3ce580c4772d9cf7da2937 [1403/1972] spi: spi-zynq-qspi: Add dual parallal and stacked support
config: arm64-buildonly-randconfig-r001-20211004 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c0039de2953d15815448b4b3c3bafb45607781e0)
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
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://github.com/Xilinx/linux-xlnx/commit/0ee2a65f834c5d35ad3ce580c4772d9cf7da2937
git remote add xilinx-xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xilinx-xlnx xlnx_rebase_v5.10
git checkout 0ee2a65f834c5d35ad3ce580c4772d9cf7da2937
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=arm64
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 >>):
In file included from drivers/spi/spi-mem.c:10:
In file included from include/linux/mtd/spi-nor.h:10:
>> include/linux/mtd/cfi.h:62:2: warning: No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work. [-W#warnings]
#warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work.
^
1 warning generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MXC_CLK_SCU
Depends on COMMON_CLK && ARCH_MXC && IMX_SCU && HAVE_ARM_SMCCC
Selected by
- CLK_IMX8QXP && COMMON_CLK && (ARCH_MXC && ARM64 || COMPILE_TEST && IMX_SCU && HAVE_ARM_SMCCC
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, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34879 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2021-10-05 7:33 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=202110051540.hVkTkh04-lkp@intel.com \
--to=lkp@intel.com \
--cc=amit.kumar-mahapatra@xilinx.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=monstr@monstr.eu \
--cc=naga.sureshkumar.relli@xilinx.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).