linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 22:16:57 +0200	[thread overview]
Message-ID: <20200723201657.nb5dm2aqmjnizmpq@duo.ucw.cz> (raw)
In-Reply-To: <30b1f173-c687-9fe2-92bd-fc53f776cb77@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

Hi!

> > > > Many network devices have LEDs with green and orange color, instead of
> > > > green and yellow.
> > > 
> > > Is it likely that we see device having both yellow and orange LEDs?
> > 
> > Why should we?
> 
> This question actually refers to the below sentence...
> 
> > > I'd simply lie and say those LEDs are yellow...
> 
> So, why do you think we should strive to limit the number
> of color definitions?

Because there's infinitely many colors :-). And programmers are bad at
differentiating them. You can't really tell wavelength of light by
looking at it.

I mean.. yes, maybe we can add orange, pink, green-blue, violet,
... white at different temperatures ...

It will be rather long list.

									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 --]

  reply	other threads:[~2020-07-23 20:17 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 [this message]
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
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=20200723201657.nb5dm2aqmjnizmpq@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).