From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [tip:auto-latest 23/37] kernel/smpboot.c:164:36: sparse: incorrect type in initializer (different ad
Date: Tue, 14 Aug 2012 20:38:47 +0000 [thread overview]
Message-ID: <20120814203847.GC20732@localhost> (raw)
Hi Thomas,
FYI, there are new sparse warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git auto-latest
head: e42942691c8262b7fe2a7b88577623082b988217
commit: f97f8f06a49febbc3cb3635172efbe64ddc79700 [23/37] smpboot: Provide infrastructure for percpu hotplug threads
All sparse warnings:
kernel/smpboot.c:23:8: sparse: symbol 'idle_threads' was not declared. Should it be static?
+ kernel/smpboot.c:164:36: sparse: incorrect type in initializer (different address spaces)
kernel/smpboot.c:164:36: expected void const [noderef] <asn:3>*__vpp_verify
kernel/smpboot.c:164:36: got struct task_struct [noderef] <asn:3>**<noident>
kernel/smpboot.c:164:35: sparse: incorrect type in initializer (different address spaces)
kernel/smpboot.c:164:35: expected struct task_struct *tsk
kernel/smpboot.c:164:35: got struct task_struct [noderef] <asn:3>*<noident>
kernel/smpboot.c:184:10: sparse: incorrect type in initializer (different address spaces)
kernel/smpboot.c:184:10: expected void const [noderef] <asn:3>*__vpp_verify
kernel/smpboot.c:184:10: got struct task_struct [noderef] <asn:3>**<noident>
+ kernel/smpboot.c:184:38: sparse: incorrect type in assignment (different address spaces)
kernel/smpboot.c:184:38: expected struct task_struct [noderef] <asn:3>*<noident>
kernel/smpboot.c:184:38: got struct task_struct *[assigned] tsk
kernel/smpboot.c:205:36: sparse: incorrect type in initializer (different address spaces)
kernel/smpboot.c:205:36: expected void const [noderef] <asn:3>*__vpp_verify
kernel/smpboot.c:205:36: got struct task_struct [noderef] <asn:3>**<noident>
kernel/smpboot.c:205:35: sparse: incorrect type in initializer (different address spaces)
kernel/smpboot.c:205:35: expected struct task_struct *tsk
kernel/smpboot.c:205:35: got struct task_struct [noderef] <asn:3>*<noident>
kernel/smpboot.c:222:36: sparse: incorrect type in initializer (different address spaces)
kernel/smpboot.c:222:36: expected void const [noderef] <asn:3>*__vpp_verify
kernel/smpboot.c:222:36: got struct task_struct [noderef] <asn:3>**<noident>
kernel/smpboot.c:222:35: sparse: incorrect type in initializer (different address spaces)
kernel/smpboot.c:222:35: expected struct task_struct *tsk
kernel/smpboot.c:222:35: got struct task_struct [noderef] <asn:3>*<noident>
kernel/smpboot.c:244:44: sparse: incorrect type in initializer (different address spaces)
kernel/smpboot.c:244:44: expected void const [noderef] <asn:3>*__vpp_verify
kernel/smpboot.c:244:44: got struct task_struct [noderef] <asn:3>**<noident>
kernel/smpboot.c:244:43: sparse: incorrect type in initializer (different address spaces)
kernel/smpboot.c:244:43: expected struct task_struct *tsk
kernel/smpboot.c:244:43: got struct task_struct [noderef] <asn:3>*<noident>
kernel/smpboot.c:249:26: sparse: incorrect type in initializer (different address spaces)
kernel/smpboot.c:249:26: expected void const [noderef] <asn:3>*__vpp_verify
kernel/smpboot.c:249:26: got struct task_struct [noderef] <asn:3>**<noident>
vim +164 kernel/smpboot.c
161 static int
162 __smpboot_create_thread(struct smp_hotplug_thread *ht, unsigned int cpu)
163 {
> 164 struct task_struct *tsk = *per_cpu_ptr(ht->store, cpu);
165 struct smpboot_thread_data *td;
166
167 if (tsk)
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
reply other threads:[~2012-08-14 20:38 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=20120814203847.GC20732@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.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 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.