From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Sven Wegener" <sven.wegener@stealer.net>
Cc: "Richard Purdie" <rpurdie@rpsys.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: Avoid needless strlen() for attributes
Date: Fri, 1 Aug 2008 13:36:22 -0700 [thread overview]
Message-ID: <2c0942db0808011336h32112df2v706a452a6db518ba@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0808012226560.2294@titan.stealer.net>
On Fri, Aug 1, 2008 at 1:30 PM, Sven Wegener <sven.wegener@stealer.net> wrote:
> There's no need for the additional call to strlen(), we can directly return the
> value returned by sprintf(). We now return a length value that doesn't include
> the final '\0', but user space shouldn't bother about it anyway.
Why not just add 1 to the return value of sprintf, and guarantee that
userspace sees the same thing before and after? It's simple enough to
do, and avoids guessing about what userspace may or may not be doing.
> Signed-off-by: Sven Wegener <sven.wegener@stealer.net>
> ---
> drivers/leds/led-class.c | 5 +----
> drivers/leds/ledtrig-timer.c | 8 ++------
> 2 files changed, 3 insertions(+), 10 deletions(-)
>
> Patch is based on your current (024e8ac) leds git tree head.
>
> diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
> index 559a408..1aa24d3 100644
> --- a/drivers/leds/led-class.c
> +++ b/drivers/leds/led-class.c
> @@ -34,14 +34,11 @@ static ssize_t led_brightness_show(struct device *dev,
> struct device_attribute *attr, char *buf)
> {
> struct led_classdev *led_cdev = dev_get_drvdata(dev);
> - ssize_t ret = 0;
>
> /* no lock needed for this */
> led_update_brightness(led_cdev);
> - sprintf(buf, "%u\n", led_cdev->brightness);
> - ret = strlen(buf) + 1;
>
> - return ret;
> + return sprintf(buf, "%u\n", led_cdev->brightness);
> }
>
> static ssize_t led_brightness_store(struct device *dev,
> diff --git a/drivers/leds/ledtrig-timer.c b/drivers/leds/ledtrig-timer.c
> index 5c99f4f..db68196 100644
> --- a/drivers/leds/ledtrig-timer.c
> +++ b/drivers/leds/ledtrig-timer.c
> @@ -70,9 +70,7 @@ static ssize_t led_delay_on_show(struct device *dev,
> struct led_classdev *led_cdev = dev_get_drvdata(dev);
> struct timer_trig_data *timer_data = led_cdev->trigger_data;
>
> - sprintf(buf, "%lu\n", timer_data->delay_on);
> -
> - return strlen(buf) + 1;
> + return sprintf(buf, "%lu\n", timer_data->delay_on);
> }
>
> static ssize_t led_delay_on_store(struct device *dev,
> @@ -116,9 +114,7 @@ static ssize_t led_delay_off_show(struct device *dev,
> struct led_classdev *led_cdev = dev_get_drvdata(dev);
> struct timer_trig_data *timer_data = led_cdev->trigger_data;
>
> - sprintf(buf, "%lu\n", timer_data->delay_off);
> -
> - return strlen(buf) + 1;
> + return sprintf(buf, "%lu\n", timer_data->delay_off);
> }
>
> static ssize_t led_delay_off_store(struct device *dev,
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2008-08-01 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 20:30 Sven Wegener
2008-08-01 20:36 ` Ray Lee [this message]
2008-08-01 20:55 ` Sven Wegener
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=2c0942db0808011336h32112df2v706a452a6db518ba@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=sven.wegener@stealer.net \
/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
all inboxes | Powered by JetHome®