From: kbuild test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [rcu:rcu/next 61/65] kernel/rcu/tasks.h:1000:37: error: 'rcu_tasks_rude' undeclared
Date: Wed, 18 Mar 2020 06:12:05 +0800 [thread overview]
Message-ID: <202003180600.DHzsYRk6%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
head: 8e97ee7a3a2a6e583619a932a0404d7ae4302dcf
commit: 589081348a37ec02d9b067aa08d4a771ae590e1e [61/65] rcu-tasks: Add RCU tasks to rcutorture writer stall output
config: mips-lemote2f_defconfig (attached as .config)
compiler: mips64el-linux-gcc (GCC) 5.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 589081348a37ec02d9b067aa08d4a771ae590e1e
# save the attached .config to linux build tree
GCC_VERSION=5.5.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from kernel/rcu/update.c:562:0:
kernel/rcu/tasks.h: In function 'show_rcu_tasks_gp_kthreads':
>> kernel/rcu/tasks.h:1000:37: error: 'rcu_tasks_rude' undeclared (first use in this function)
show_rcu_tasks_generic_gp_kthread(&rcu_tasks_rude, "");
^
kernel/rcu/tasks.h:1000:37: note: each undeclared identifier is reported only once for each function it appears in
vim +/rcu_tasks_rude +1000 kernel/rcu/tasks.h
996
997 void show_rcu_tasks_gp_kthreads(void)
998 {
999 show_rcu_tasks_generic_gp_kthread(&rcu_tasks, "");
> 1000 show_rcu_tasks_generic_gp_kthread(&rcu_tasks_rude, "");
1001 show_rcu_tasks_trace_gp_kthread();
1002 }
1003
---
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: 22135 bytes --]
reply other threads:[~2020-03-17 22:12 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=202003180600.DHzsYRk6%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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
all inboxes | Powered by JetHome®