[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20160802103935.19557-1-baolex.ni@intel.com>
Date: Tue, 2 Aug 2016 18:39:35 +0800
From: Baole Ni <baolex.ni@...el.com>
To: tim@...erelk.net, lars.ellenberg@...bit.com, pavel@....cz,
gregkh@...uxfoundation.org, hpa@...or.com, x86@...nel.org
Cc: linux-kernel@...r.kernel.org, chuansheng.liu@...el.com,
baolex.ni@...el.com
Subject: [PATCH 0087/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/block/paride/pf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/paride/pf.c b/drivers/block/paride/pf.c
index 7a7d977..4b27d65 100644
--- a/drivers/block/paride/pf.c
+++ b/drivers/block/paride/pf.c
@@ -160,7 +160,7 @@ enum {D_PRT, D_PRO, D_UNI, D_MOD, D_SLV, D_LUN, D_DLY};
static DEFINE_MUTEX(pf_mutex);
static DEFINE_SPINLOCK(pf_spin_lock);
-module_param(verbose, bool, 0644);
+module_param(verbose, bool, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
module_param(major, int, 0);
module_param(name, charp, 0);
module_param(cluster, int, 0);
--
2.9.2
Powered by blists - more mailing lists