[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20160802113148.24309-1-baolex.ni@intel.com>
Date: Tue, 2 Aug 2016 19:31:48 +0800
From: Baole Ni <baolex.ni@...el.com>
To: mchehab@...nel.org, maurochehab@...il.com, mchehab@...radead.org,
mchehab@...hat.com, m.chehab@...sung.com, hdegoede@...hat.com,
kgene@...nel.org, k.kozlowski@...sung.com
Cc: linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
chuansheng.liu@...el.com, baolex.ni@...el.com
Subject: [PATCH 0634/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/media/usb/gspca/topro.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/usb/gspca/topro.c b/drivers/media/usb/gspca/topro.c
index c028a5c..46a62ef 100644
--- a/drivers/media/usb/gspca/topro.c
+++ b/drivers/media/usb/gspca/topro.c
@@ -4979,6 +4979,6 @@ static struct usb_driver sd_driver = {
module_usb_driver(sd_driver);
-module_param(force_sensor, int, 0644);
+module_param(force_sensor, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(force_sensor,
"Force sensor. 0: cx0342, 1: soi763a");
--
2.9.2
Powered by blists - more mailing lists