From: Sakari Ailus <sakari.ailus@iki.fi>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
j.anaszewski@samsung.com
Subject: Re: [PATCH v3] led/led-class: Handle LEDs with the same name
Date: Wed, 25 Mar 2015 15:53:59 +0200 [thread overview]
Message-ID: <20150325135359.GN18321@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <CAPybu_3TKV9oK8KAww3JaMKKOy2gQbZO369C=O=W=Vk3mM5DSQ@mail.gmail.com>
On Wed, Mar 25, 2015 at 02:22:53PM +0100, Ricardo Ribalda Delgado wrote:
> Hi Sakari!
> >> Regarding s/dev_info/dev_warn : Do you want to send the patch or I should do it?
> >
> > Is this one merged already? If yes, sure I can. Otherwise a new version
> > would be nice.
> It is at least here
>
> https://git.kernel.org/cgit/linux/kernel/git/cooloney/linux-leds.git/commit/?h=devel&id=0767f8c5c53018f8cc7d87871abb7d3290be7596
>
> and here
>
> https://git.kernel.org/cgit/linux/kernel/git/cooloney/linux-leds.git/commit/?h=for-next&id=0767f8c5c53018f8cc7d87871abb7d3290be7596
I'll send a patch. Thanks!
--
Sakari Ailus
e-mail: sakari.ailus@iki.fi XMPP: sailus@retiisi.org.uk
next prev parent reply other threads:[~2015-03-25 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 23:05 [PATCH v3] led/led-class: Handle LEDs with the same name Ricardo Ribalda Delgado
2015-03-25 0:54 ` Sakari Ailus
2015-03-25 9:20 ` Ricardo Ribalda Delgado
2015-03-25 13:02 ` Sakari Ailus
2015-03-25 13:22 ` Ricardo Ribalda Delgado
2015-03-25 13:53 ` Sakari Ailus [this message]
2015-03-25 18:33 ` Bryan Wu
2015-03-26 23:30 ` Sakari Ailus
2015-03-27 8:09 ` Ricardo Ribalda Delgado
2015-03-27 17:24 ` Bryan Wu
2015-03-28 1:07 ` Fengguang Wu
2015-06-08 22:55 ` Kees Cook
2015-06-26 9:19 ` Geert Uytterhoeven
2015-06-26 17:47 ` Kees Cook
2015-03-30 7:59 ` Geert Uytterhoeven
2015-03-30 8:35 ` Ricardo Ribalda Delgado
2015-03-30 8:43 ` Geert Uytterhoeven
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=20150325135359.GN18321@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--cc=cooloney@gmail.com \
--cc=j.anaszewski@samsung.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox