[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20130420095450.GA24488@localhost>
Date: Sat, 20 Apr 2013 17:54:50 +0800
From: Fengguang Wu <fengguang.wu@...el.com>
To: Rodolfo Giometti <giometti@...eenne.com>
Cc: Alexander Gordeev <lasaine@....cs.msu.su>,
linux-kernel@...r.kernel.org
Subject: [PATCH] pps: pps_kc_hardpps_lock can be static
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@...el.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists