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/staging/wlan-ng/prism2sta.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/wlan-ng/prism2sta.c
b/drivers/staging/wlan-ng/prism2sta.c
index 64f9072..eff5f6b 100644
--- a/drivers/staging/wlan-ng/prism2sta.c
+++ b/drivers/staging/wlan-ng/prism2sta.c
@@ -88,12 +88,12 @@ int prism2_reset_settletime = 100; /* Reset settle time in
ms */
static int prism2_doreset; /* Do a reset at init? */
-module_param(prism2_doreset, int, 0644);
+module_param(prism2_doreset, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(prism2_doreset, "Issue a reset on initialization");
-module_param(prism2_reset_holdtime, int, 0644);
+module_param(prism2_reset_holdtime, int, S_IRUSR | S_IWUSR | S_IRGRP |
S_IROTH);
MODULE_PARM_DESC(prism2_reset_holdtime, "reset hold time in ms");
-module_param(prism2_reset_settletime, int, 0644);
+module_param(prism2_reset_settletime, int, S_IRUSR | S_IWUSR | S_IRGRP |
S_IROTH);
MODULE_PARM_DESC(prism2_reset_settletime, "reset settle time in ms");
MODULE_LICENSE("Dual MPL/GPL");
--
2.9.2
_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
