[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20160802105240.29942-1-baolex.ni@intel.com>
Date: Tue, 2 Aug 2016 18:52:40 +0800
From: Baole Ni <baolex.ni@...el.com>
To: alexander.shishkin@...ux.intel.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-kernel@...r.kernel.org, chuansheng.liu@...el.com,
baolex.ni@...el.com, aduggan@...aptics.com, dianders@...omium.org
Subject: [PATCH 0243/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/hwtracing/stm/heartbeat.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/hwtracing/stm/heartbeat.c b/drivers/hwtracing/stm/heartbeat.c
index 3da7b67..92b3726 100644
--- a/drivers/hwtracing/stm/heartbeat.c
+++ b/drivers/hwtracing/stm/heartbeat.c
@@ -26,8 +26,8 @@
static int nr_devs = 4;
static int interval_ms = 10;
-module_param(nr_devs, int, 0400);
-module_param(interval_ms, int, 0600);
+module_param(nr_devs, int, S_IRUSR);
+module_param(interval_ms, int, S_IRUSR | S_IWUSR);
static struct stm_heartbeat {
struct stm_source_data data;
--
2.9.2
Powered by blists - more mailing lists