From: Conor Dooley <conor@kernel.org>
To: Owen O'Hehir <oo.hehir@gmail.com>
Cc: e@freeshell.de, kernel@esmil.dk, conor.dooley@microchip.com,
robh@kernel.org, krzk+dt@kernel.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: starfive: jh7110-common: keep the status power LED on
Date: Sun, 8 Nov 2026 23:24:30 +0000 [thread overview]
Message-ID: <20261108-florist-smartness-eeaaf38d5d1a@spud> (raw)
In-Reply-To: <CALp3LZ5Vwhx-CqKz7Jr+VE+e0S1EyNO_-OA-uC0h_dz0VF0r_g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
On Sun, Nov 08, 2026 at 09:55:07PM +0000, Owen O'Hehir wrote:
> Hi Conor,
>
> You may have missed my email on Friday at 21:12.
>
> I think E has a point. There is a separate red LED on the board that
> shows power. My confusion came from the net that drives this green LED,
> which is labelled STS_PWR. This green LED has no silkscreen label and the
> schematic is ambiguous on this particular LED.
>
> It is probably better to drop this patch. Apologies again.
Okay, no worries.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-11-08 23:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 18:40 Owen O'Hehir
2026-11-06 18:51 ` E Shattow
2026-11-06 19:59 ` Owen O'Hehir
2026-11-06 20:30 ` E Shattow
2026-11-06 21:12 ` Owen O'Hehir
2026-11-06 21:13 ` Owen O'Hehir
2026-11-06 18:54 ` Conor Dooley
2026-11-06 19:06 ` E Shattow
2026-11-06 21:15 ` Conor Dooley
2026-11-07 14:05 ` E Shattow
2026-11-08 21:55 ` Owen O'Hehir
2026-11-08 23:24 ` Conor Dooley [this message]
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=20261108-florist-smartness-eeaaf38d5d1a@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=e@freeshell.de \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oo.hehir@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@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
all inboxes | Powered by JetHome®