* [PATCH] pps: pps_kc_hardpps_lock can be static
@ 2013-04-20 9:54 Fengguang Wu
0 siblings, 0 replies; only message in thread
From: Fengguang Wu @ 2013-04-20 9:54 UTC (permalink / raw)
To: Rodolfo Giometti; +Cc: Alexander Gordeev, linux-kernel
drivers/pps/kc.c:37:1: sparse: symbol 'pps_kc_hardpps_lock' was not declared. Should it be static?
drivers/pps/kc.c:39:19: sparse: symbol 'pps_kc_hardpps_dev' was not declared. Should it be static?
drivers/pps/kc.c:40:5: sparse: symbol 'pps_kc_hardpps_mode' was not declared. Should it be static?
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
drivers/pps/kc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- linux-next.orig/drivers/pps/kc.c 2012-02-23 14:54:18.218537076 +0800
+++ linux-next/drivers/pps/kc.c 2013-04-20 17:20:18.866632025 +0800
@@ -34,10 +34,10 @@
*/
/* state variables to bind kernel consumer */
-DEFINE_SPINLOCK(pps_kc_hardpps_lock);
+static DEFINE_SPINLOCK(pps_kc_hardpps_lock);
/* PPS API (RFC 2783): current source and mode for kernel consumer */
-struct pps_device *pps_kc_hardpps_dev; /* unique pointer to device */
-int pps_kc_hardpps_mode; /* mode bits for kernel consumer */
+static struct pps_device *pps_kc_hardpps_dev; /* unique pointer to device */
+static int pps_kc_hardpps_mode; /* mode bits for kernel consumer */
/* pps_kc_bind - control PPS kernel consumer binding
* @pps: the PPS source
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-04-20 9:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-20 9:54 [PATCH] pps: pps_kc_hardpps_lock can be static Fengguang Wu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox