From: Shuah Khan <shuahkhan@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: shuahkhan@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
rpurdie@linux.intel.com
Subject: Re: [PATCH] leds: simple_strtoul-cleanup
Date: Mon, 09 Apr 2012 08:26:04 -0600 [thread overview]
Message-ID: <1333981564.2871.1.camel@lorien2> (raw)
In-Reply-To: <1333916453.1801.2.camel@joe2Laptop>
On Sun, 2012-04-08 at 13:20 -0700, Joe Perches wrote:
> On Sun, 2012-04-08 at 14:13 -0600, Shuah Khan wrote:
> > led-class.c and ledtri-timer.c still use simple_strtoul().
> > Change leds to use kstrtoul() instead of obsolete simple_strtoul().
> []
> > @@ -44,23 +44,19 @@ static ssize_t led_brightness_store(struct device *dev,
> > struct device_attribute *attr, const char *buf, size_t size)
> []
> > diff --git a/drivers/leds/ledtrig-timer.c b/drivers/leds/ledtrig-timer.c
> > @@ -31,21 +31,18 @@ static ssize_t led_delay_on_store(struct device *dev,
> > struct device_attribute *attr, const char *buf, size_t size)
> []
> > static ssize_t led_delay_off_show(struct device *dev,
> []
> > +out:
> > + return size;
>
> These now don't return -EINVAL, is that a problem
> for any caller?
I looked at the other _store() interfaces in leds - there is no
consistent EINVAL return. However, it would be an easy change to make to
have these return EINVAL in case of error like they used to. I can send
an updated patch.
-- Shuah
next prev parent reply other threads:[~2012-04-09 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-08 20:13 [PATCH] leds: simple_strtoul-cleanup Shuah Khan
2012-04-08 20:20 ` Joe Perches
2012-04-09 14:26 ` Shuah Khan [this message]
2012-04-09 16:11 ` [PATCH v2] " Shuah Khan
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=1333981564.2871.1.camel@lorien2 \
--to=shuahkhan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@linux.intel.com \
/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