[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20160802115354.8044-1-baolex.ni@intel.com>
Date: Tue, 2 Aug 2016 19:53:54 +0800
From: Baole Ni <baolex.ni@...el.com>
To: lgirdwood@...il.com, broonie@...nel.org, paulus@...ba.org,
mpe@...erman.id.au, dwmw2@...radead.org, m.chehab@...sung.com,
pawel@...iak.com, m.szyprowski@...sung.com,
kyungmin.park@...sung.com, k.kozlowski@...sung.com
Cc: linux-kernel@...r.kernel.org, chuansheng.liu@...el.com,
baolex.ni@...el.com
Subject: [PATCH 0871/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/regulator/userspace-consumer.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/userspace-consumer.c b/drivers/regulator/userspace-consumer.c
index 765acc1..8ca7629 100644
--- a/drivers/regulator/userspace-consumer.c
+++ b/drivers/regulator/userspace-consumer.c
@@ -92,8 +92,8 @@ static ssize_t reg_set_state(struct device *dev, struct device_attribute *attr,
return count;
}
-static DEVICE_ATTR(name, 0444, reg_show_name, NULL);
-static DEVICE_ATTR(state, 0644, reg_show_state, reg_set_state);
+static DEVICE_ATTR(name, S_IRUSR | S_IRGRP | S_IROTH, reg_show_name, NULL);
+static DEVICE_ATTR(state, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH, reg_show_state, reg_set_state);
static struct attribute *attributes[] = {
&dev_attr_name.attr,
--
2.9.2
Powered by blists - more mailing lists