[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20160802104640.25338-1-baolex.ni@intel.com>
Date: Tue, 2 Aug 2016 18:46:40 +0800
From: Baole Ni <baolex.ni@...el.com>
To: rubini@...dd.com, ccross@...roid.com, keescook@...omium.org,
tony.luck@...el.com, matt@...eblueprint.co.uk,
m.chehab@...sung.com, lho@....com, dougthompson@...ssion.com,
bp@...en8.de
Cc: linux-kernel@...r.kernel.org, chuansheng.liu@...el.com,
baolex.ni@...el.com, lee.jones@...aro.org
Subject: [PATCH 0174/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/fmc/fmc-fakedev.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/fmc/fmc-fakedev.c b/drivers/fmc/fmc-fakedev.c
index 941d093..2ace110 100644
--- a/drivers/fmc/fmc-fakedev.c
+++ b/drivers/fmc/fmc-fakedev.c
@@ -26,11 +26,11 @@
/* The user can pass up to 4 names of eeprom images to load */
static char *ff_eeprom[FF_MAX_MEZZANINES];
static int ff_nr_eeprom;
-module_param_array_named(eeprom, ff_eeprom, charp, &ff_nr_eeprom, 0444);
+module_param_array_named(eeprom, ff_eeprom, charp, &ff_nr_eeprom, S_IRUSR | S_IRGRP | S_IROTH);
/* The user can ask for a multi-mezzanine carrier, with the default eeprom */
static int ff_nr_dev = 1;
-module_param_named(ndev, ff_nr_dev, int, 0444);
+module_param_named(ndev, ff_nr_dev, int, S_IRUSR | S_IRGRP | S_IROTH);
/* Lazily, don't support the "standard" module parameters */
--
2.9.2
Powered by blists - more mailing lists