All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Behun <marek.behun@nic.cz>
To: Pavel Machek <pavel@ucw.cz>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	linux-leds@vger.kernel.org, Dan Murphy <dmurphy@ti.com>
Subject: Re: [PATCH] leds: add orange color
Date: Thu, 23 Jul 2020 23:24:34 +0200	[thread overview]
Message-ID: <20200723232434.1871c4fa@nic.cz> (raw)
In-Reply-To: <20200723231755.6b6476c0@nic.cz>

On Thu, 23 Jul 2020 23:17:55 +0200
Marek Behun <marek.behun@nic.cz> wrote:

> LOL, so I looked into schematics and the manufacturer of the ethernet
> port cage calls the LED yellow. So apparently I confused it with
> orange... :D
> 
> http://www.link-pp.com/?product/201807116277.html
> see LED Option in the table

OK so I think we can ignore this "orange" color proposal now, sorry
for taking your time.

I would really appreciate though if we could talk about the road I took
in v2 of the RFC "Add support for LEDs on Marvell PHYs", as compared to
the road in v1. That is a real problem... :D

Marek

  reply	other threads:[~2020-07-23 21:24 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
2020-07-23 21:17                 ` Marek Behun
2020-07-23 21:24                   ` Marek Behun [this message]
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=20200723232434.1871c4fa@nic.cz \
    --to=marek.behun@nic.cz \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.