linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: Richard Purdie <rpurdie@rpsys.net>, Bryan Wu <cooloney@gmail.com>,
	Simon Que <sque@chromium.org>,
	Olof Johansson <olofj@chromium.org>,
	Duncan Laurie <dlaurie@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: Add Chrome OS keyboard backlight LEDs driver
Date: Fri, 4 Mar 2016 11:19:36 -0800	[thread overview]
Message-ID: <20160304191936.GB17145@dtor-ws> (raw)
In-Reply-To: <56D95790.9080301@samsung.com>

Hi Jacek,

On Fri, Mar 04, 2016 at 10:38:24AM +0100, Jacek Anaszewski wrote:
> Hi Dmitry,
> 
> Thanks for the patch. There's already other pending version [1],
> still to be decided where it should live.
> 
> [1] http://comments.gmane.org/gmane.linux.leds/4523

Yes, sorry, have not noticed it already being submitted while doing some
spring cleaning.

I mentioned in the other message what I think Evan needs to change in
his version to make it match this one.

Thanks.

-- 
Dmitry

  reply	other threads:[~2016-03-04 19:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 23:46 [PATCH] leds: Add Chrome OS keyboard backlight LEDs driver Dmitry Torokhov
2016-03-04  8:38 ` Evan McClain
2016-03-04  9:38   ` Jacek Anaszewski
2016-03-04 19:13     ` Dmitry Torokhov
2016-03-04 20:41       ` Evan McClain
2016-03-04 20:56         ` Dmitry Torokhov
2016-03-04 22:09           ` Olof Johansson
2016-03-04 20:55       ` Jacek Anaszewski
2016-03-04 20:59         ` Dmitry Torokhov
2016-03-04 21:48           ` Jacek Anaszewski
2016-03-04  9:38 ` Jacek Anaszewski
2016-03-04 19:19   ` Dmitry Torokhov [this message]
2016-03-04 19:22     ` Olof Johansson

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=20160304191936.GB17145@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=cooloney@gmail.com \
    --cc=dlaurie@chromium.org \
    --cc=groeck@chromium.org \
    --cc=j.anaszewski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=olofj@chromium.org \
    --cc=rpurdie@rpsys.net \
    --cc=sque@chromium.org \
    /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).