From: kbuild test robot <fengguang.wu@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: [tip:timers/core 2/2] kernel/time/hrtimer.c:444:9: sparse: symbol '__hrtimer_get_next_event' was not declared. Should it be static?
Date: Fri, 23 Jan 2015 20:12:06 +0800 [thread overview]
Message-ID: <201501232056.e6Qrox8m%fengguang.wu@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core
head: 9bc7491906b4113b4c5ae442157c7dfc4e10cd14
commit: 9bc7491906b4113b4c5ae442157c7dfc4e10cd14 [2/2] hrtimer: Prevent stale expiry time in hrtimer_interrupt()
reproduce:
# apt-get install sparse
git checkout 9bc7491906b4113b4c5ae442157c7dfc4e10cd14
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
kernel/time/hrtimer.c:67:1: sparse: symbol '__pcpu_scope_hrtimer_bases' was not declared. Should it be static?
>> kernel/time/hrtimer.c:444:9: sparse: symbol '__hrtimer_get_next_event' was not declared. Should it be static?
kernel/time/hrtimer.c:152:27: sparse: context imbalance in 'lock_hrtimer_base' - wrong count at exit
kernel/time/hrtimer.c:994:25: sparse: context imbalance in '__hrtimer_start_range_ns' - unexpected unlock
kernel/time/hrtimer.c:793:9: sparse: context imbalance in 'hrtimer_try_to_cancel' - unexpected unlock
kernel/time/hrtimer.c:1099:9: sparse: context imbalance in 'hrtimer_get_remaining' - unexpected unlock
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
next reply other threads:[~2015-01-23 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 12:12 kbuild test robot [this message]
2015-01-23 12:12 ` [PATCH tip] hrtimer: __hrtimer_get_next_event() can be static kbuild test robot
2015-01-24 10:00 ` [tip:timers/core] hrtimer: Make __hrtimer_get_next_event() static tip-bot for kbuild test robot
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=201501232056.e6Qrox8m%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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®