From: Dan Murphy <dmurphy@ti.com>
To: Randy Dunlap <rdunlap@infradead.org>,
<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: Tue, 24 Mar 2020 13:52:24 -0500 [thread overview]
Message-ID: <e600d433-7af2-c939-db69-29369180392d@ti.com> (raw)
In-Reply-To: <e9d6c050-0ee4-6829-bd23-25e9bbf72774@infradead.org>
Randy
On 3/24/20 1:41 PM, Randy Dunlap wrote:
> On 3/24/20 11:14 AM, Dan Murphy wrote:
>> diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
>> index d82f1dea3711..37dcdb06a29b 100644
>> --- a/drivers/leds/Kconfig
>> +++ b/drivers/leds/Kconfig
>> @@ -30,6 +30,16 @@ config LEDS_CLASS_FLASH
>> for the flash related features of a LED device. It can be built
>> as a module.
>>
>> +config LEDS_CLASS_MULTI_COLOR
>> + tristate "LED Mulit Color LED Class Support"
> Multi
> or even MultiColor
> or Multicolor
Thanks for the spell check. I cannot believe this made it through so
many reviews. hehe
Dan
next prev parent reply other threads:[~2020-03-24 18:58 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 [this message]
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
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=e600d433-7af2-c939-db69-29369180392d@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 \
--cc=rdunlap@infradead.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).