[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160802105158.29348-1-baolex.ni@intel.com>
Date: Tue, 2 Aug 2016 18:51:58 +0800
From: Baole Ni <baolex.ni@...el.com>
To: hdegoede@...hat.com, jdelvare@...e.com, linux@...ck-us.net,
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 0234/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/abituguru.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/abituguru.c b/drivers/hwmon/abituguru.c
index 7a09c16..84d7070 100644
--- a/drivers/hwmon/abituguru.c
+++ b/drivers/hwmon/abituguru.c
@@ -194,7 +194,7 @@ MODULE_PARM_DESC(pwms, "Number of PWMs on the uGuru "
/* Default verbose is 2, since this driver is still in the testing phase */
static int verbose = 2;
-module_param(verbose, int, 0644);
+module_param(verbose, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(verbose, "How verbose should the driver be? (0-3):\n"
" 0 normal output\n"
" 1 + verbose error reporting\n"
--
2.9.2
Powered by blists - more mailing lists