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 <[email protected]> Signed-off-by: Baole Ni <[email protected]> --- drivers/fmc/fmc-dump.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/fmc/fmc-dump.c b/drivers/fmc/fmc-dump.c index c91afd6..224cd60 100644 --- a/drivers/fmc/fmc-dump.c +++ b/drivers/fmc/fmc-dump.c @@ -14,9 +14,9 @@ #include <linux/fmc-sdb.h> static int fmc_must_dump_eeprom; -module_param_named(dump_eeprom, fmc_must_dump_eeprom, int, 0644); +module_param_named(dump_eeprom, fmc_must_dump_eeprom, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH); static int fmc_must_dump_sdb; -module_param_named(dump_sdb, fmc_must_dump_sdb, int, 0644); +module_param_named(dump_sdb, fmc_must_dump_sdb, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH); #define LINELEN 16 -- 2.9.2
