[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20160802104116.20951-1-baolex.ni@intel.com>
Date: Tue, 2 Aug 2016 18:41:16 +0800
From: Baole Ni <baolex.ni@...el.com>
To: arnd@...db.de, gregkh@...uxfoundation.org, johan.hedberg@...il.com,
hpa@...or.com, x86@...nel.org
Cc: linux-kernel@...r.kernel.org, chuansheng.liu@...el.com,
baolex.ni@...el.com, jslaby@...e.cz, peter@...sgaard.com,
lee.jones@...aro.org
Subject: [PATCH 0108/1285] Replace numeric parameter like 0444 with macro
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the corresponding macro,
and that using macro can improve the robustness and readability of the code,
thus, I suggest replacing the numeric parameter with the macro.
Signed-off-by: Chuansheng Liu <chuansheng.liu@...el.com>
Signed-off-by: Baole Ni <baolex.ni@...el.com>
---
drivers/char/mmtimer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/char/mmtimer.c b/drivers/char/mmtimer.c
index 3d6c067..ca0850d 100644
--- a/drivers/char/mmtimer.c
+++ b/drivers/char/mmtimer.c
@@ -249,7 +249,7 @@ static struct mmtimer_node *timers;
static unsigned mmtimer_interval_retry_increment =
MMTIMER_INTERVAL_RETRY_INCREMENT_DEFAULT;
-module_param(mmtimer_interval_retry_increment, uint, 0644);
+module_param(mmtimer_interval_retry_increment, uint, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(mmtimer_interval_retry_increment,
"RTC ticks to add to expiration on interval retry (default 40)");
--
2.9.2
Powered by blists - more mailing lists