[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20160802114913.4366-1-baolex.ni@intel.com>
Date: Tue, 2 Aug 2016 19:49:13 +0800
From: Baole Ni <baolex.ni@...el.com>
To: sudipm.mukherjee@...il.com, deller@....de, Allen.Hubbe@....com,
rjui@...adcom.com, sbranden@...adcom.com, m.chehab@...sung.com,
pawel@...iak.com, m.szyprowski@...sung.com,
kyungmin.park@...sung.com, k.kozlowski@...sung.com
Cc: linux-kernel@...r.kernel.org, chuansheng.liu@...el.com,
baolex.ni@...el.com, arnd@...db.de
Subject: [PATCH 0816/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/parport/parport_pc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/parport/parport_pc.c b/drivers/parport/parport_pc.c
index 78530d1..7d5d30e 100644
--- a/drivers/parport/parport_pc.c
+++ b/drivers/parport/parport_pc.c
@@ -3160,7 +3160,7 @@ module_param_array(dma, charp, NULL, 0);
#if defined(CONFIG_PARPORT_PC_SUPERIO) || \
(defined(CONFIG_PARPORT_1284) && defined(CONFIG_PARPORT_PC_FIFO))
MODULE_PARM_DESC(verbose_probing, "Log chit-chat during initialisation");
-module_param(verbose_probing, int, 0644);
+module_param(verbose_probing, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
#endif
#ifdef CONFIG_PCI
static char *init_mode;
--
2.9.2
Powered by blists - more mailing lists