From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [zen-kernel-zen-kernel:5.5/muqss 1/16] kernel/sched/MuQSS.c:139:36: error: 'CONFIG_SHARERQ' undeclared here (not in a function); did you mean 'CONFIG_SH_ETH'?
Date: Thu, 06 Feb 2020 11:17:22 +0800 [thread overview]
Message-ID: <202002061114.DuXzyHda%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
tree: https://github.com/zen-kernel/zen-kernel 5.5/muqss
head: ac994d428ce6eaa4c05a2b4a2083a32fcc55c682
commit: 3cb8dbe8f826f89701118d44389146736d96d4f7 [1/16] MultiQueue Skiplist Scheduler v0.198
config: m68k-allyesconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 3cb8dbe8f826f89701118d44389146736d96d4f7
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=m68k
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> kernel/sched/MuQSS.c:139:36: error: 'CONFIG_SHARERQ' undeclared here (not in a function); did you mean 'CONFIG_SH_ETH'?
static int rqshare __read_mostly = CONFIG_SHARERQ; /* Default RQSHARE_MC */
^~~~~~~~~~~~~~
CONFIG_SH_ETH
vim +139 kernel/sched/MuQSS.c
134
135 /*
136 * This determines what level of runqueue sharing will be done and is
137 * configurable at boot time with the bootparam rqshare =
138 */
> 139 static int rqshare __read_mostly = CONFIG_SHARERQ; /* Default RQSHARE_MC */
140
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 52098 bytes --]
reply other threads:[~2020-02-06 3:17 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=202002061114.DuXzyHda%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.