[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALiw-2HRoRb+ZX3C90KCg2-ky9XcrDeuTh3dJeLvyp1ypJ8Vkw@mail.gmail.com>
Date: Fri, 4 Mar 2016 11:22:48 -0800
From: Olof Johansson <olofj@...omium.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Jacek Anaszewski <j.anaszewski@...sung.com>,
Richard Purdie <rpurdie@...ys.net>,
Bryan Wu <cooloney@...il.com>, Simon Que <sque@...omium.org>,
Duncan Laurie <dlaurie@...omium.org>,
Guenter Roeck <groeck@...omium.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-leds@...r.kernel.org
Subject: Re: [PATCH] leds: Add Chrome OS keyboard backlight LEDs driver
2016-03-04 11:19 GMT-08:00 Dmitry Torokhov <dmitry.torokhov@...il.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.
Part of the reason for this is that discoverability of the patch was
low -- it was only ever sent on linux-leds and no other list.
Cc:ing lkml is useful since most of us are subscribed to it and a
quick search for patches will find it. In addition to the subsystem
list of course, since subsystem maintainers don't want to have to
monitor all of LKML for patches to their code.
-Olof
Powered by blists - more mailing lists