From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tony O'Brien <Tony.OBrien@alliedtelesis.co.nz>
Cc: "pavel@kernel.org" <pavel@kernel.org>,
"lee@kernel.org" <lee@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
Ben Hoelker <Ben.Hoelker@alliedtelesis.co.nz>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Subject: Re: [PATCH] dt-bindings:leds: Add function define for POE
Date: Mon, 17 Feb 2025 10:13:13 +0100 [thread overview]
Message-ID: <7462bb47-01ff-45d7-9cbc-24b8da7f7a1d@kernel.org> (raw)
In-Reply-To: <31bc5340976761dbf3653ed2802a8988e07b18d5.camel@alliedtelesis.co.nz>
On 16/02/2025 22:37, Tony O'Brien wrote:
> Hi Krzysztof -
>
>> Where did these two reviews happen?
> They were in-house reviews. Please feel free to remove them from the
> patch.
>
>> Where is any user of this?
> We are adding Kernel control of PoE LEDs and thought this might be
> useful to others, maybe those working on netdev, or anyone implementing
> PoE on their devices. Also, the Kernel >> Docs >> LEDs page states:
> "If required color or function is missing, please submit a patch to
> linux-leds@vger.kernel.org", which is included here.
You did not answer: where is the user? By "we are adding" you mean
downstream?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-17 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 0:58 [PATCH] Add function define for PoE Tony O'Brien
2025-02-13 0:58 ` [PATCH] dt-bindings:leds: Add function define for POE Tony O'Brien
2025-02-13 9:31 ` Krzysztof Kozlowski
2025-02-16 21:37 ` Tony O'Brien
2025-02-17 9:13 ` Krzysztof Kozlowski [this message]
2025-02-23 20:54 ` Chris Packham
2025-02-24 8:11 ` Krzysztof Kozlowski
2025-02-24 19:59 ` Chris Packham
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=7462bb47-01ff-45d7-9cbc-24b8da7f7a1d@kernel.org \
--to=krzk@kernel.org \
--cc=Ben.Hoelker@alliedtelesis.co.nz \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Tony.OBrien@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=robh@kernel.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