From: kernel test robot <lkp@intel.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jcmvbkbc-xtensa:xtensa-5.18-esp32 39/45] include/linux/mtd/xip.h:68:2: warning: #warning "missing IRQ and timer primitives for XIP MTD support"
Date: Sat, 4 Jun 2022 19:30:58 +0800 [thread overview]
Message-ID: <202206041901.y4FClYBn-lkp@intel.com> (raw)
tree: https://github.com/jcmvbkbc/linux-xtensa xtensa-5.18-esp32
head: 137adeae90088411fe27a1be624afd8336542302
commit: 91e595b15206abdfdc74585230f5c11ff7e1c3ab [39/45] WIP: xtensa: add XIP-aware MTD support
config: xtensa-allyesconfig (https://download.01.org/0day-ci/archive/20220604/202206041901.y4FClYBn-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 11.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/jcmvbkbc/linux-xtensa/commit/91e595b15206abdfdc74585230f5c11ff7e1c3ab
git remote add jcmvbkbc-xtensa https://github.com/jcmvbkbc/linux-xtensa
git fetch --no-tags jcmvbkbc-xtensa xtensa-5.18-esp32
git checkout 91e595b15206abdfdc74585230f5c11ff7e1c3ab
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=xtensa SHELL=/bin/bash drivers/mtd/chips/ fs/ kernel/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from drivers/mtd/chips/cfi_probe.c:16:
>> include/linux/mtd/xip.h:68:2: warning: #warning "missing IRQ and timer primitives for XIP MTD support" [-Wcpp]
68 | #warning "missing IRQ and timer primitives for XIP MTD support"
| ^~~~~~~
>> include/linux/mtd/xip.h:69:2: warning: #warning "some of the XIP MTD support code will be disabled" [-Wcpp]
69 | #warning "some of the XIP MTD support code will be disabled"
| ^~~~~~~
>> include/linux/mtd/xip.h:70:2: warning: #warning "your system will therefore be unresponsive when writing or erasing flash" [-Wcpp]
70 | #warning "your system will therefore be unresponsive when writing or erasing flash"
| ^~~~~~~
--
In file included from include/linux/mtd/cfi.h:16,
from drivers/mtd/chips/cfi_cmdset_0002.c:39:
>> include/linux/mtd/xip.h:68:2: warning: #warning "missing IRQ and timer primitives for XIP MTD support" [-Wcpp]
68 | #warning "missing IRQ and timer primitives for XIP MTD support"
| ^~~~~~~
>> include/linux/mtd/xip.h:69:2: warning: #warning "some of the XIP MTD support code will be disabled" [-Wcpp]
69 | #warning "some of the XIP MTD support code will be disabled"
| ^~~~~~~
>> include/linux/mtd/xip.h:70:2: warning: #warning "your system will therefore be unresponsive when writing or erasing flash" [-Wcpp]
70 | #warning "your system will therefore be unresponsive when writing or erasing flash"
| ^~~~~~~
drivers/mtd/chips/cfi_cmdset_0002.c: In function 'xip_udelay':
>> drivers/mtd/chips/cfi_cmdset_0002.c:1070:34: warning: variable 'start' set but not used [-Wunused-but-set-variable]
1070 | unsigned long suspended, start = xip_currtime();
| ^~~~~
>> drivers/mtd/chips/cfi_cmdset_0002.c:1070:23: warning: variable 'suspended' set but not used [-Wunused-but-set-variable]
1070 | unsigned long suspended, start = xip_currtime();
| ^~~~~~~~~
--
In file included from drivers/mtd/chips/cfi_cmdset_0001.c:33:
>> include/linux/mtd/xip.h:68:2: warning: #warning "missing IRQ and timer primitives for XIP MTD support" [-Wcpp]
68 | #warning "missing IRQ and timer primitives for XIP MTD support"
| ^~~~~~~
>> include/linux/mtd/xip.h:69:2: warning: #warning "some of the XIP MTD support code will be disabled" [-Wcpp]
69 | #warning "some of the XIP MTD support code will be disabled"
| ^~~~~~~
>> include/linux/mtd/xip.h:70:2: warning: #warning "your system will therefore be unresponsive when writing or erasing flash" [-Wcpp]
70 | #warning "your system will therefore be unresponsive when writing or erasing flash"
| ^~~~~~~
drivers/mtd/chips/cfi_cmdset_0001.c: In function 'xip_wait_for_operation':
>> drivers/mtd/chips/cfi_cmdset_0001.c:1148:40: warning: variable 'start' set but not used [-Wunused-but-set-variable]
1148 | unsigned long usec, suspended, start, done;
| ^~~~~
>> drivers/mtd/chips/cfi_cmdset_0001.c:1148:29: warning: variable 'suspended' set but not used [-Wunused-but-set-variable]
1148 | unsigned long usec, suspended, start, done;
| ^~~~~~~~~
vim +68 include/linux/mtd/xip.h
^1da177e4c3f41 Linus Torvalds 2005-04-16 67
^1da177e4c3f41 Linus Torvalds 2005-04-16 @68 #warning "missing IRQ and timer primitives for XIP MTD support"
^1da177e4c3f41 Linus Torvalds 2005-04-16 @69 #warning "some of the XIP MTD support code will be disabled"
^1da177e4c3f41 Linus Torvalds 2005-04-16 @70 #warning "your system will therefore be unresponsive when writing or erasing flash"
^1da177e4c3f41 Linus Torvalds 2005-04-16 71
:::::: The code at line 68 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-04 11:31 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=202206041901.y4FClYBn-lkp@intel.com \
--to=lkp@intel.com \
--cc=jcmvbkbc@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox