[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191218100720.2420401-1-ben.dooks@codethink.co.uk>
Date: Wed, 18 Dec 2019 10:07:20 +0000
From: "Ben Dooks (Codethink)" <ben.dooks@...ethink.co.uk>
To: ben.dooks@...ethink.co.uk
Cc: Benson Leung <bleung@...omium.org>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
Guenter Roeck <groeck@...omium.org>,
linux-kernel@...r.kernel.org
Subject: [PATCH] platform/chrome: cros-ec: make init_lock static
The init_lock is not declared or used outside of cros_ec_ishtp.c
so make it static to avoid the following warning:
drivers/platform/chrome/cros_ec_ishtp.c:79:1: warning: symbol 'init_lock' was not declared. Should it be static?
Signed-off-by: Ben Dooks (Codethink) <ben.dooks@...ethink.co.uk>
---
Cc: Benson Leung <bleung@...omium.org>
Cc: Enric Balletbo i Serra <enric.balletbo@...labora.com>
Cc: Guenter Roeck <groeck@...omium.org>
Cc: linux-kernel@...r.kernel.org
---
drivers/platform/chrome/cros_ec_ishtp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/platform/chrome/cros_ec_ishtp.c b/drivers/platform/chrome/cros_ec_ishtp.c
index e5996821d08b..5f8e76f3022a 100644
--- a/drivers/platform/chrome/cros_ec_ishtp.c
+++ b/drivers/platform/chrome/cros_ec_ishtp.c
@@ -76,7 +76,7 @@ struct cros_ish_in_msg {
*
* The writers are .reset() and .probe() function.
*/
-DECLARE_RWSEM(init_lock);
+static DECLARE_RWSEM(init_lock);
/**
* struct response_info - Encapsulate firmware response related
--
2.24.0
Powered by blists - more mailing lists