From: Dan Murphy <dmurphy@ti.com>
To: <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>
Cc: <linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Dan Murphy <dmurphy@ti.com>
Subject: [PATCH v10 15/16] leds: lp55xx: Fix checkpatch file permissions issues
Date: Tue, 1 Oct 2019 09:56:19 -0500 [thread overview]
Message-ID: <20191001145620.11123-16-dmurphy@ti.com> (raw)
In-Reply-To: <20191001145620.11123-1-dmurphy@ti.com>
Fix the checkpatch warnings for the use of the file permission macros.
In converting the file permissions to the DEVICE_ATTR_XX macros the
call back function names needed to be updated within the code.
This means that the lp55xx_ needed to be dropped in the name to keep in
harmony with the ABI documentation.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
---
drivers/leds/leds-lp55xx-common.c | 22 ++++++++++------------
1 file changed, 10 insertions(+), 12 deletions(-)
diff --git a/drivers/leds/leds-lp55xx-common.c b/drivers/leds/leds-lp55xx-common.c
index 5de4f1789a44..87bf25795c87 100644
--- a/drivers/leds/leds-lp55xx-common.c
+++ b/drivers/leds/leds-lp55xx-common.c
@@ -78,7 +78,7 @@ static int lp55xx_post_init_device(struct lp55xx_chip *chip)
return cfg->post_init_device(chip);
}
-static ssize_t lp55xx_show_current(struct device *dev,
+static ssize_t led_current_show(struct device *dev,
struct device_attribute *attr,
char *buf)
{
@@ -87,7 +87,7 @@ static ssize_t lp55xx_show_current(struct device *dev,
return scnprintf(buf, PAGE_SIZE, "%d\n", led->led_current);
}
-static ssize_t lp55xx_store_current(struct device *dev,
+static ssize_t led_current_store(struct device *dev,
struct device_attribute *attr,
const char *buf, size_t len)
{
@@ -111,7 +111,7 @@ static ssize_t lp55xx_store_current(struct device *dev,
return len;
}
-static ssize_t lp55xx_show_max_current(struct device *dev,
+static ssize_t max_current_show(struct device *dev,
struct device_attribute *attr,
char *buf)
{
@@ -120,9 +120,8 @@ static ssize_t lp55xx_show_max_current(struct device *dev,
return scnprintf(buf, PAGE_SIZE, "%d\n", led->max_current);
}
-static DEVICE_ATTR(led_current, S_IRUGO | S_IWUSR, lp55xx_show_current,
- lp55xx_store_current);
-static DEVICE_ATTR(max_current, S_IRUGO , lp55xx_show_max_current, NULL);
+static DEVICE_ATTR_RW(led_current);
+static DEVICE_ATTR_RO(max_current);
static struct attribute *lp55xx_led_attrs[] = {
&dev_attr_led_current.attr,
@@ -281,7 +280,7 @@ static int lp55xx_request_firmware(struct lp55xx_chip *chip)
GFP_KERNEL, chip, lp55xx_firmware_loaded);
}
-static ssize_t lp55xx_show_engine_select(struct device *dev,
+static ssize_t select_engine_show(struct device *dev,
struct device_attribute *attr,
char *buf)
{
@@ -291,7 +290,7 @@ static ssize_t lp55xx_show_engine_select(struct device *dev,
return sprintf(buf, "%d\n", chip->engine_idx);
}
-static ssize_t lp55xx_store_engine_select(struct device *dev,
+static ssize_t select_engine_store(struct device *dev,
struct device_attribute *attr,
const char *buf, size_t len)
{
@@ -333,7 +332,7 @@ static inline void lp55xx_run_engine(struct lp55xx_chip *chip, bool start)
chip->cfg->run_engine(chip, start);
}
-static ssize_t lp55xx_store_engine_run(struct device *dev,
+static ssize_t run_engine_store(struct device *dev,
struct device_attribute *attr,
const char *buf, size_t len)
{
@@ -358,9 +357,8 @@ static ssize_t lp55xx_store_engine_run(struct device *dev,
return len;
}
-static DEVICE_ATTR(select_engine, S_IRUGO | S_IWUSR,
- lp55xx_show_engine_select, lp55xx_store_engine_select);
-static DEVICE_ATTR(run_engine, S_IWUSR, NULL, lp55xx_store_engine_run);
+static DEVICE_ATTR_RW(select_engine);
+static DEVICE_ATTR_WO(run_engine);
static struct attribute *lp55xx_engine_attributes[] = {
&dev_attr_select_engine.attr,
--
2.22.0.214.g8dca754b1e
next prev parent reply other threads:[~2019-10-01 14:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 14:56 [PATCH v10 00/16] Multicolor Framework Dan Murphy
2019-10-01 14:56 ` [PATCH v10 01/16] dt: bindings: Add multicolor class dt bindings documention Dan Murphy
2019-10-01 14:56 ` [PATCH v10 02/16] dt-bindings: leds: Add multicolor ID to the color ID list Dan Murphy
2019-10-01 14:56 ` [PATCH v10 03/16] " Dan Murphy
2019-10-01 14:56 ` [PATCH v10 04/16] leds: multicolor: Introduce a multicolor class definition Dan Murphy
2019-10-06 15:23 ` Jacek Anaszewski
2019-10-07 11:51 ` Dan Murphy
2019-10-01 14:56 ` [PATCH v10 05/16] dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers Dan Murphy
2019-10-01 14:56 ` [PATCH v10 06/16] leds: lp50xx: Add the LP50XX family of the RGB LED driver Dan Murphy
2019-10-02 0:16 ` kbuild test robot
2019-10-06 16:12 ` Jacek Anaszewski
2019-10-07 12:35 ` Dan Murphy
2019-10-01 14:56 ` [PATCH v10 07/16] dt: bindings: lp55xx: Be consistent in the document with LED acronym Dan Murphy
2019-10-01 14:56 ` [PATCH v10 08/16] dt: bindings: lp55xx: Update binding for Multicolor Framework Dan Murphy
2019-10-01 14:56 ` [PATCH v10 09/16] ARM: dts: n900: Add reg property to the LP5523 channel node Dan Murphy
2019-10-01 14:56 ` [PATCH v10 10/16] ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 " Dan Murphy
2019-10-01 14:56 ` [PATCH v10 11/16] ARM: dts: ste-href: Add reg property to the LP5521 channel nodes Dan Murphy
2019-10-04 21:50 ` Linus Walleij
2019-10-01 14:56 ` [PATCH v10 12/16] leds: lp55xx: Add multicolor framework support to lp55xx Dan Murphy
2019-10-02 0:31 ` kbuild test robot
2019-10-02 1:24 ` kbuild test robot
2019-10-06 19:52 ` Jacek Anaszewski
2019-10-07 17:08 ` Dan Murphy
2019-10-07 19:27 ` Jacek Anaszewski
2019-10-01 14:56 ` [PATCH v10 13/16] leds: lp5523: Update the lp5523 code to add intensity function Dan Murphy
2019-10-01 14:56 ` [PATCH v10 14/16] leds: lp5521: Add multicolor framework intensity support Dan Murphy
2019-10-01 14:56 ` Dan Murphy [this message]
2019-10-01 14:56 ` [PATCH v10 16/16] leds: lp5523: Fix checkpatch issues in the code Dan Murphy
2019-10-02 15:53 ` [PATCH v10 00/16] Multicolor Framework Dan Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191001145620.11123-16-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).