[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20160802105231.29810-1-baolex.ni@intel.com>
Date: Tue, 2 Aug 2016 18:52:31 +0800
From: Baole Ni <baolex.ni@...el.com>
To: linux@...ck-us.net, jdelvare@...e.com, airlied@...ux.ie,
kgene@...nel.org, k.kozlowski@...sung.com,
dougthompson@...ssion.com, bp@...en8.de
Cc: linux-hwmon@...r.kernel.org, linux-kernel@...r.kernel.org,
chuansheng.liu@...el.com, baolex.ni@...el.com,
aduggan@...aptics.com, dianders@...omium.org
Subject: [PATCH 0241/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/hwmon/pmbus/zl6100.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/pmbus/zl6100.c b/drivers/hwmon/pmbus/zl6100.c
index 771802d..369d3b3 100644
--- a/drivers/hwmon/pmbus/zl6100.c
+++ b/drivers/hwmon/pmbus/zl6100.c
@@ -59,7 +59,7 @@ struct zl6100_data {
#define ZL6100_WAIT_TIME 1000 /* uS */
static ushort delay = ZL6100_WAIT_TIME;
-module_param(delay, ushort, 0644);
+module_param(delay, ushort, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(delay, "Delay between chip accesses in uS");
/* Convert linear sensor value to milli-units */
--
2.9.2
Powered by blists - more mailing lists