From: kbuild test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: kbuild-all@01.org, paulmck@linux.vnet.ibm.com,
catalin.marinas@arm.com, dennis.chen@arm.com,
jiangshanlai@gmail.com, josh@joshtriplett.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
mathieu.desnoyers@efficios.com, rostedt@goodmis.org,
steve.capper@arm.com, will.deacon@arm.com
Subject: Re: [PATCHv2] rcu: tree: correctly handle sparse possible CPUs
Date: Fri, 20 May 2016 18:30:15 +0800 [thread overview]
Message-ID: <201605201819.JjEW9UVy%fengguang.wu@intel.com> (raw)
In-Reply-To: <1463480530-5674-1-git-send-email-mark.rutland@arm.com>
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]
Hi,
[auto build test ERROR on rcu/rcu/next]
[cannot apply to v4.6 next-20160519]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Mark-Rutland/rcu-tree-correctly-handle-sparse-possible-CPUs/20160517-182533
base: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
config: x86_64-randconfig-s5-05172218 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the linux-review/Mark-Rutland/rcu-tree-correctly-handle-sparse-possible-CPUs/20160517-182533 HEAD 63c5ae5d92c6952c029738ca1dd3382ce8b1cf4d builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
In file included from kernel/rcu/tree.c:4209:0:
kernel/rcu/tree_plugin.h: In function 'rcu_boost_kthread_setaffinity':
kernel/rcu/tree_plugin.h:1168:2: error: implicit declaration of function 'for_each_leaf_node_cpu_bit' [-Werror=implicit-function-declaration]
for_each_leaf_node_cpu_bit(rnp, cpu, bit)
^~~~~~~~~~~~~~~~~~~~~~~~~~
>> kernel/rcu/tree_plugin.h:1169:3: error: expected ';' before 'if'
if ((mask & bit) && cpu != outgoingcpu)
^~
kernel/rcu/tree_plugin.h:1159:16: warning: unused variable 'mask' [-Wunused-variable]
unsigned long mask = rcu_rnp_online_cpus(rnp);
^~~~
cc1: some warnings being treated as errors
vim +1169 kernel/rcu/tree_plugin.h
1162 int cpu;
1163
1164 if (!t)
1165 return;
1166 if (!zalloc_cpumask_var(&cm, GFP_KERNEL))
1167 return;
> 1168 for_each_leaf_node_cpu_bit(rnp, cpu, bit)
> 1169 if ((mask & bit) && cpu != outgoingcpu)
1170 cpumask_set_cpu(cpu, cm);
1171 if (cpumask_weight(cm) == 0)
1172 cpumask_setall(cm);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 27939 bytes --]
next prev parent reply other threads:[~2016-05-20 10:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 16:48 [PATCH] " Mark Rutland
2016-05-16 19:19 ` Paul E. McKenney
2016-05-17 10:22 ` [PATCHv2] " Mark Rutland
2016-05-17 19:01 ` Paul E. McKenney
2016-05-13 1:27 ` Mark Rutland
2016-05-18 0:12 ` Paul E. McKenney
2016-05-18 12:02 ` Arnd Bergmann
2016-05-18 18:15 ` Mark Rutland
2016-05-18 18:41 ` Paul E. McKenney
2016-05-20 10:30 ` kbuild test robot [this message]
2016-05-18 15:15 ` [PATCH] " Andrey Ryabinin
2016-05-18 18:01 ` Paul E. McKenney
2016-05-18 18:30 ` Mark Rutland
2016-05-18 18:44 ` Paul E. McKenney
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=201605201819.JjEW9UVy%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=catalin.marinas@arm.com \
--cc=dennis.chen@arm.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=steve.capper@arm.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®