[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20160802122640.30665-1-baolex.ni@intel.com>
Date: Tue, 2 Aug 2016 20:26:40 +0800
From: Baole Ni <baolex.ni@...el.com>
To: perex@...ex.cz, tiwai@...e.com, serge@...lyn.com,
davem@...emloft.net, kadlec@...ckhole.kfki.hu,
m.szyprowski@...sung.com, kyungmin.park@...sung.com,
k.kozlowski@...sung.com
Cc: alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
chuansheng.liu@...el.com, baolex.ni@...el.com,
aryabinin@...tuozzo.com
Subject: [PATCH 1207/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>
---
sound/pci/als300.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/sound/pci/als300.c b/sound/pci/als300.c
index add3176..8c24c5a 100644
--- a/sound/pci/als300.c
+++ b/sound/pci/als300.c
@@ -105,11 +105,11 @@ static int index[SNDRV_CARDS] = SNDRV_DEFAULT_IDX;
static char *id[SNDRV_CARDS] = SNDRV_DEFAULT_STR;
static bool enable[SNDRV_CARDS] = SNDRV_DEFAULT_ENABLE_PNP;
-module_param_array(index, int, NULL, 0444);
+module_param_array(index, int, NULL, S_IRUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(index, "Index value for ALS300 sound card.");
-module_param_array(id, charp, NULL, 0444);
+module_param_array(id, charp, NULL, S_IRUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(id, "ID string for ALS300 sound card.");
-module_param_array(enable, bool, NULL, 0444);
+module_param_array(enable, bool, NULL, S_IRUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(enable, "Enable ALS300 sound card.");
struct snd_als300 {
--
2.9.2
Powered by blists - more mailing lists