LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* [tip:timers/core 2/2] kernel/time/hrtimer.c:444:9: sparse: symbol '__hrtimer_get_next_event' was not declared. Should it be static?
@ 2015-01-23 12:12 kbuild test robot
  2015-01-23 12:12 ` [PATCH tip] hrtimer: __hrtimer_get_next_event() can be static kbuild test robot
  0 siblings, 1 reply; 3+ messages in thread
From: kbuild test robot @ 2015-01-23 12:12 UTC (permalink / raw)
  To: Thomas Gleixner; +Cc: kbuild-all, linux-kernel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [PATCH tip] hrtimer: __hrtimer_get_next_event() can be static
  2015-01-23 12:12 [tip:timers/core 2/2] kernel/time/hrtimer.c:444:9: sparse: symbol '__hrtimer_get_next_event' was not declared. Should it be static? kbuild test robot
@ 2015-01-23 12:12 ` kbuild test robot
  2015-01-24 10:00   ` [tip:timers/core] hrtimer: Make __hrtimer_get_next_event() static tip-bot for kbuild test robot
  0 siblings, 1 reply; 3+ messages in thread
From: kbuild test robot @ 2015-01-23 12:12 UTC (permalink / raw)
  To: Thomas Gleixner; +Cc: kbuild-all, linux-kernel

kernel/time/hrtimer.c:444:9: sparse: symbol '__hrtimer_get_next_event' was not declared. Should it be static?

Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
 hrtimer.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c
index b663653..702dce8 100644
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -441,7 +441,7 @@ static inline void debug_deactivate(struct hrtimer *timer)
 }
 
 #if defined(CONFIG_NO_HZ_COMMON) || defined(CONFIG_HIGH_RES_TIMERS)
-ktime_t __hrtimer_get_next_event(struct hrtimer_cpu_base *cpu_base)
+static ktime_t __hrtimer_get_next_event(struct hrtimer_cpu_base *cpu_base)
 {
 	struct hrtimer_clock_base *base = cpu_base->clock_base;
 	ktime_t expires, expires_next = { .tv64 = KTIME_MAX };

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [tip:timers/core] hrtimer: Make __hrtimer_get_next_event() static
  2015-01-23 12:12 ` [PATCH tip] hrtimer: __hrtimer_get_next_event() can be static kbuild test robot
@ 2015-01-24 10:00   ` tip-bot for kbuild test robot
  0 siblings, 0 replies; 3+ messages in thread
From: tip-bot for kbuild test robot @ 2015-01-24 10:00 UTC (permalink / raw)
  To: linux-tip-commits; +Cc: tglx, linux-kernel, mingo, hpa, fengguang.wu

Commit-ID:  4ebbda5251374d532ba8939de4241d769d1420b6
Gitweb:     http://git.kernel.org/tip/4ebbda5251374d532ba8939de4241d769d1420b6
Author:     kbuild test robot <fengguang.wu@intel.com>
AuthorDate: Fri, 23 Jan 2015 20:12:06 +0800
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Sat, 24 Jan 2015 10:53:36 +0100

hrtimer: Make __hrtimer_get_next_event() static

kernel/time/hrtimer.c:444:9: sparse: symbol '__hrtimer_get_next_event' was not declared. Should it be static?

Fixes: 9bc7491906b4 hrtimer: Prevent stale expiry time in hrtimer_interrupt()
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Cc: kbuild-all@01.org
Link: http://lkml.kernel.org/r/20150123121206.GA4766@snb
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 kernel/time/hrtimer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c
index b67ebea..ce8221a 100644
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -441,7 +441,7 @@ static inline void debug_deactivate(struct hrtimer *timer)
 }
 
 #if defined(CONFIG_NO_HZ_COMMON) || defined(CONFIG_HIGH_RES_TIMERS)
-ktime_t __hrtimer_get_next_event(struct hrtimer_cpu_base *cpu_base)
+static ktime_t __hrtimer_get_next_event(struct hrtimer_cpu_base *cpu_base)
 {
 	struct hrtimer_clock_base *base = cpu_base->clock_base;
 	ktime_t expires, expires_next = { .tv64 = KTIME_MAX };

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-01-24 10:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-01-23 12:12 [tip:timers/core 2/2] kernel/time/hrtimer.c:444:9: sparse: symbol '__hrtimer_get_next_event' was not declared. Should it be static? kbuild test robot
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).