All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Wu <cooloney@gmail.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: Richard Purdie <rpurdie@rpsys.net>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH 0/3] leds/class: Fix string handling
Date: Mon, 30 Mar 2015 10:15:20 -0700	[thread overview]
Message-ID: <CAK5ve-LyQx6s53+kuh7h0mAwFrz65i-z2nf82dsme=Y-Uk7p7g@mail.gmail.com> (raw)
In-Reply-To: <1427705712-18083-1-git-send-email-ricardo.ribalda@gmail.com>

On Mon, Mar 30, 2015 at 1:55 AM, Ricardo Ribalda Delgado
<ricardo.ribalda@gmail.com> wrote:
> Fix errors reported by Geert Uytterhoeven.
>
> I didn't have the chance to test the changes it in real hardware.
>
>

Thanks, Geert and Ricardo.
Ricardo, do you mind folding your fixing patches with original one
together and send it out again? I will use the new one to replace that
one in my tree, since this patch is not merged into Linus tree yet.

-Bryan


> Ricardo Ribalda Delgado (3):
>   leds/class: Use strlcpy instead of strncpy
>   leds/class: Check snprintf return value
>   leds/class: Set naming index as unsigned
>
>  drivers/leds/led-class.c | 14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)
>
> --
> 2.1.4
>

  parent reply	other threads:[~2015-03-30 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30  8:55 [PATCH 0/3] leds/class: Fix string handling Ricardo Ribalda Delgado
2015-03-30  8:55 ` [PATCH 1/3] leds/class: Use strlcpy instead of strncpy Ricardo Ribalda Delgado
2015-03-30  8:55 ` [PATCH 2/3] leds/class: Check snprintf return value Ricardo Ribalda Delgado
2015-03-30  8:59   ` Geert Uytterhoeven
2015-03-30  8:55 ` [PATCH 3/3] leds/class: Set naming index as unsigned Ricardo Ribalda Delgado
2015-03-30  8:59   ` Geert Uytterhoeven
2015-03-30 17:15 ` Bryan Wu [this message]
2015-03-30 17:46   ` [PATCH 0/3] leds/class: Fix string handling Ricardo Ribalda Delgado
2015-03-30 18:11     ` Bryan Wu

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='CAK5ve-LyQx6s53+kuh7h0mAwFrz65i-z2nf82dsme=Y-Uk7p7g@mail.gmail.com' \
    --to=cooloney@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=ricardo.ribalda@gmail.com \
    --cc=rpurdie@rpsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.