From: Dan Murphy <dmurphy@ti.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>
Cc: <linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v18 4/4] leds: multicolor: Introduce a multicolor class definition
Date: Sun, 29 Mar 2020 16:09:43 -0500 [thread overview]
Message-ID: <0db08bd0-ae6f-049a-7970-cbaf2b1654e3@ti.com> (raw)
In-Reply-To: <ea7915a1-91ea-43d5-2e96-99d1ecc49875@gmail.com>
Jacek
On 3/29/20 1:43 PM, Jacek Anaszewski wrote:
> Dan,
>
> On 3/29/20 5:14 PM, Dan Murphy wrote:
<snip>
>
>> Dan
>>
I will wait to hear from Pavel on this patchset since the array
definition was something he was asking for.
Need to make sure this was his intent on wanting the array vs the sysfs
interfaces otherwise the changes maybe futile in nature.
Dan
next prev parent reply other threads:[~2020-03-29 21:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 18:14 [PATCH v18 0/4] Multi Color LED Framework Patches Dan Murphy
2020-03-24 18:14 ` [PATCH v18 1/4] dt: bindings: Add multicolor class dt bindings documention Dan Murphy
2020-03-24 18:14 ` [PATCH v18 2/4] dt-bindings: leds: Add multicolor ID to the color ID list Dan Murphy
2020-03-24 18:14 ` [PATCH v18 3/4] " Dan Murphy
2020-03-24 18:14 ` [PATCH v18 4/4] leds: multicolor: Introduce a multicolor class definition Dan Murphy
2020-03-24 18:41 ` Randy Dunlap
2020-03-24 18:52 ` Dan Murphy
2020-03-28 14:03 ` Jacek Anaszewski
2020-03-28 21:31 ` Dan Murphy
2020-03-29 12:47 ` Jacek Anaszewski
2020-03-29 15:14 ` Dan Murphy
2020-03-29 18:43 ` Jacek Anaszewski
2020-03-29 21:09 ` Dan Murphy [this message]
2020-06-04 13:21 ` Pavel Machek
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=0db08bd0-ae6f-049a-7970-cbaf2b1654e3@ti.com \
--to=dmurphy@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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