From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [zen-kernel-zen-kernel:5.13/zen-sauce 1/4] mm/vmscan.c:188:55: error: 'CONFIG_CLEAN_LOW_KBYTES' undeclared here (not in a function); did you mean 'CONFIG_LEDS_SPI_BYTE'?
Date: Fri, 23 Jul 2021 14:28:33 +0800 [thread overview]
Message-ID: <202107231430.aYI02Wsr-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2918 bytes --]
tree: https://github.com/zen-kernel/zen-kernel 5.13/zen-sauce
head: efe513d7401c0d8ee779944de9997da960e257ce
commit: aec8f00a3066a2589dd6ea97d5f86d81c8d40c4a [1/4] mm/vmscan: add sysctl knobs for protecting clean cache
config: nios2-randconfig-r034-20210719 (attached as .config)
compiler: nios2-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/zen-kernel/zen-kernel/commit/aec8f00a3066a2589dd6ea97d5f86d81c8d40c4a
git remote add zen-kernel-zen-kernel https://github.com/zen-kernel/zen-kernel
git fetch --no-tags zen-kernel-zen-kernel 5.13/zen-sauce
git checkout aec8f00a3066a2589dd6ea97d5f86d81c8d40c4a
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross O=build_dir ARCH=nios2 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
>> mm/vmscan.c:180:5: warning: "CONFIG_CLEAN_LOW_KBYTES" is not defined, evaluates to 0 [-Wundef]
180 | #if CONFIG_CLEAN_LOW_KBYTES < 0
| ^~~~~~~~~~~~~~~~~~~~~~~
>> mm/vmscan.c:184:5: warning: "CONFIG_CLEAN_MIN_KBYTES" is not defined, evaluates to 0 [-Wundef]
184 | #if CONFIG_CLEAN_MIN_KBYTES < 0
| ^~~~~~~~~~~~~~~~~~~~~~~
>> mm/vmscan.c:188:55: error: 'CONFIG_CLEAN_LOW_KBYTES' undeclared here (not in a function); did you mean 'CONFIG_LEDS_SPI_BYTE'?
188 | unsigned long sysctl_clean_low_kbytes __read_mostly = CONFIG_CLEAN_LOW_KBYTES;
| ^~~~~~~~~~~~~~~~~~~~~~~
| CONFIG_LEDS_SPI_BYTE
>> mm/vmscan.c:189:55: error: 'CONFIG_CLEAN_MIN_KBYTES' undeclared here (not in a function); did you mean 'CONFIG_LEDS_SPI_BYTE'?
189 | unsigned long sysctl_clean_min_kbytes __read_mostly = CONFIG_CLEAN_MIN_KBYTES;
| ^~~~~~~~~~~~~~~~~~~~~~~
| CONFIG_LEDS_SPI_BYTE
vim +188 mm/vmscan.c
179
> 180 #if CONFIG_CLEAN_LOW_KBYTES < 0
181 #error "CONFIG_CLEAN_LOW_KBYTES must be >= 0"
182 #endif
183
> 184 #if CONFIG_CLEAN_MIN_KBYTES < 0
185 #error "CONFIG_CLEAN_MIN_KBYTES must be >= 0"
186 #endif
187
> 188 unsigned long sysctl_clean_low_kbytes __read_mostly = CONFIG_CLEAN_LOW_KBYTES;
> 189 unsigned long sysctl_clean_min_kbytes __read_mostly = CONFIG_CLEAN_MIN_KBYTES;
190
---
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: 29337 bytes --]
reply other threads:[~2021-07-23 6:28 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=202107231430.aYI02Wsr-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@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.