From: Xincheng Ji <jixincheng@ultrarisc.com>
To: Conor Dooley <conor@kernel.org>
Cc: Xincheng Ji <jixincheng@ultrarisc.com>,
sashiko-reviews@lists.linux.dev, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 7/7] riscv: dts: ultrarisc: Add Milk-V Titan board device tree
Date: Thu, 22 Oct 2026 09:21:03 +0800 [thread overview]
Message-ID: <179263206397.701068.17555028009758516675.b4-reply@b4> (raw)
In-Reply-To: <20261021-badly-issuing-847ac366c9b9@spud>
Hi Conor,
On 2026-10-21 17:51 +0100, Conor Dooley wrote:
> > >
> > > Because led_parse_fwnode_props() returns early when label is present, the
> > > color and function properties on led@1 and led@2 are never parsed and are
> > > completely ignored at runtime.
> > >
> > > In addition, Documentation/devicetree/bindings/leds/common.yaml deprecates
> > > label for new bindings in favor of color and function.
> > >
> > > Would it make sense to remove label from both nodes so that the LED core
> > > uses color and function to compose the standard LED names?
> You're asking a bot that will never reply to you.
>
> I'd say that if the analysis provided is correct, then yes you should
> since the deprecated property overrides the replacement properties.
Thanks for the clarification and for reviewing the patch. Sorry for
addressing my previous question to the bot; I hadn't realised it would
not respond to follow-up questions.
I'll remove the two LED label properties in the next revision so that
color and function are used for naming.
Best regards,
Xincheng
--
Xincheng Ji <jixincheng@ultrarisc.com>
next prev parent reply other threads:[~2026-10-22 1:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 7:55 [PATCH v4 0/7] riscv: Add device tree support for UltraRISC DP1000 Xincheng Ji via B4 Relay
2026-10-19 7:55 ` [PATCH v4 1/7] dt-bindings: vendor-prefixes: Add shenrongda Xincheng Ji via B4 Relay
2026-10-19 7:55 ` [PATCH v4 2/7] dt-bindings: riscv: cpus: Add UltraRISC CP100 compatible Xincheng Ji via B4 Relay
2026-10-19 7:55 ` [PATCH v4 3/7] dt-bindings: riscv: Add UltraRISC DP1000 board compatibles Xincheng Ji via B4 Relay
2026-10-19 7:55 ` [PATCH v4 4/7] dt-bindings: timer: Add UltraRISC DP1000 CLINT Xincheng Ji via B4 Relay
2026-10-19 7:55 ` [PATCH v4 5/7] riscv: dts: ultrarisc: Add initial device tree for UltraRISC DP1000 Xincheng Ji via B4 Relay
2026-10-19 7:55 ` [PATCH v4 6/7] riscv: dts: ultrarisc: Add Shenzhen Rongda M0 board device tree Xincheng Ji via B4 Relay
2026-10-19 7:55 ` [PATCH v4 7/7] riscv: dts: ultrarisc: Add Milk-V Titan " Xincheng Ji via B4 Relay
2026-10-19 8:08 ` sashiko-bot
2026-10-20 1:43 ` Xincheng Ji
2026-10-21 16:51 ` Conor Dooley
2026-10-22 1:21 ` Xincheng Ji [this message]
2026-10-22 18:17 ` Conor Dooley
2026-10-23 1:11 ` Xincheng Ji
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=179263206397.701068.17555028009758516675.b4-reply@b4 \
--to=jixincheng@ultrarisc.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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