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....@intel.com>
Signed-off-by: Baole Ni <baolex...@intel.com>
---
 drivers/scsi/mpt3sas/mpt3sas_base.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/scsi/mpt3sas/mpt3sas_base.c 
b/drivers/scsi/mpt3sas/mpt3sas_base.c
index 751f13e..d9cc7c2 100644
--- a/drivers/scsi/mpt3sas/mpt3sas_base.c
+++ b/drivers/scsi/mpt3sas/mpt3sas_base.c
@@ -122,7 +122,7 @@ _scsih_set_fwfault_debug(const char *val, struct 
kernel_param *kp)
        return 0;
 }
 module_param_call(mpt3sas_fwfault_debug, _scsih_set_fwfault_debug,
-       param_get_int, &mpt3sas_fwfault_debug, 0644);
+       param_get_int, &mpt3sas_fwfault_debug, S_IRUSR | S_IWUSR | S_IRGRP | 
S_IROTH);
 
 /**
  *  mpt3sas_remove_dead_ioc_func - kthread context to remove dead ioc
-- 
2.9.2

Reply via email to