From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [tip:auto-latest 25/37] kernel/softirq.c:843:36: sparse: incorrect type in initializer (different ad
Date: Tue, 14 Aug 2012 20:38:57 +0000 [thread overview]
Message-ID: <20120814203857.GD20732@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: 3e339b5dae24a7065e196eb8d0145ab2f8cc2d2d [25/37] softirq: Use hotplug thread infrastructure
All sparse warnings:
kernel/softirq.c:408:8: sparse: symbol 'tasklet_vec' was not declared. Should it be static?
kernel/softirq.c:409:8: sparse: symbol 'tasklet_hi_vec' was not declared. Should it be static?
+ kernel/softirq.c:843:36: sparse: incorrect type in initializer (different address spaces)
kernel/softirq.c:843:36: expected struct task_struct [noderef] <asn:3>**store
kernel/softirq.c:843:36: got struct task_struct *[noderef] [toplevel] <asn:3>*<noident>
vim +843 kernel/softirq.c
840 };
841
842 static struct smp_hotplug_thread softirq_threads = {
> 843 .store = &ksoftirqd,
844 .thread_should_run = ksoftirqd_should_run,
845 .thread_fn = run_ksoftirqd,
846 .thread_comm = "ksoftirqd/%u",
---
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=20120814203857.GD20732@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.