From: kbuild test robot <fengguang.wu@intel.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: [rcu:rcu/next 116/116] kernel/cpu.c:1833: warning: unused variable 'cpu'
Date: Wed, 21 Jun 2017 12:16:38 +0800 [thread overview]
Message-ID: <201706211236.BHDRAkLb%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
head: faeb334286b762ba6b829ad62e3d39a97674bb56
commit: faeb334286b762ba6b829ad62e3d39a97674bb56 [116/116] rcu: Migrate callbacks earlier in the CPU-offline timeline
config: x86_64-randconfig-b0-06210849 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
git checkout faeb334286b762ba6b829ad62e3d39a97674bb56
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
kernel/cpu.c: In function 'boot_cpu_state_init':
>> kernel/cpu.c:1833: warning: unused variable 'cpu'
vim +/cpu +1833 kernel/cpu.c
1817 /* Mark the boot cpu "present", "online" etc for SMP and UP case */
1818 set_cpu_online(cpu, true);
1819 set_cpu_active(cpu, true);
1820 set_cpu_present(cpu, true);
1821 set_cpu_possible(cpu, true);
1822
1823 #ifdef CONFIG_SMP
1824 __boot_cpu_id = cpu;
1825 #endif
1826 }
1827
1828 /*
1829 * Must be called _AFTER_ setting up the per_cpu areas
1830 */
1831 void __init boot_cpu_state_init(void)
1832 {
> 1833 int cpu;
1834
1835 per_cpu_ptr(&cpuhp_state, smp_processor_id())->state = CPUHP_ONLINE;
1836 #ifdef CONFIG_SMP
1837 for_each_possible_cpu(cpu)
1838 per_cpu_ptr(&cpuhp_state, cpu)->cpu = cpu;
1839 #endif
1840 }
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 22169 bytes --]
reply other threads:[~2017-06-21 4:07 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=201706211236.BHDRAkLb%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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®