From: Pavel Machek <pavel@ucw.cz>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: "Marek Behún" <marek.behun@nic.cz>,
linux-leds@vger.kernel.org, "Dan Murphy" <dmurphy@ti.com>
Subject: Re: [PATCH] leds: add orange color
Date: Thu, 23 Jul 2020 23:04:52 +0200 [thread overview]
Message-ID: <20200723210452.c63oup3k7w4icqc6@duo.ucw.cz> (raw)
In-Reply-To: <854ee2f0-4dd1-b665-f216-bff33ab3b571@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
> > ...but really, unless there's device where there are leds of
> > yellow/orange color... it may be easier to keep the current list.
>
> Yellow has been available since the inception of the led_colors array,
> so if we have that, then why we should not have orange?
I fear people will confuse yellow and orange.
> > IOW "are we solving real problem by introducing orange color"?
>
> Yes, we allow to accurately describe LEDs available
> on the market.
That should not be our goal.
If we wanted accurate description, it would be wavelength in nm for
monochrome LEDs. (Incidentally, that's what manufacturers use and we
may want to do that for RGB LEDs).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-07-23 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 12:57 [PATCH] leds: add orange color Marek Behún
2020-07-23 13:40 ` Dan Murphy
2020-07-23 13:47 ` Marek Behún
2020-07-23 14:23 ` Dan Murphy
2020-07-23 19:39 ` Pavel Machek
2020-07-23 20:09 ` Jacek Anaszewski
2020-07-23 20:11 ` Jacek Anaszewski
2020-07-23 20:16 ` Pavel Machek
2020-07-23 20:31 ` Jacek Anaszewski
2020-07-23 20:39 ` Pavel Machek
2020-07-23 20:54 ` Dan Murphy
2020-07-23 20:57 ` Jacek Anaszewski
2020-07-23 21:04 ` Pavel Machek [this message]
2020-07-23 21:17 ` Marek Behun
2020-07-23 21:24 ` Marek Behun
2020-07-23 21:38 ` 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=20200723210452.c63oup3k7w4icqc6@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=marek.behun@nic.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;
as well as URLs for NNTP newsgroup(s).