From: "Rafał Miłecki" <zajec5@gmail.com>
To: Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Rob Herring <robh+dt@kernel.org>
Cc: "Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH] dt-bindings: leds: leds-gpio: fix & extend node regex
Date: Wed, 10 Mar 2021 08:00:25 +0100 [thread overview]
Message-ID: <20210310070025.9150-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
The old regex allowed only 1 character to follow the "led-" prefix which
was most likely just an overlook. Fix it and while at it allow dashes in
node names. It allows more meaningful names and it helpful e.g. when
having the same function name with 2 different colors. For example:
1. led-power-white
2. led-power-blue
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
Documentation/devicetree/bindings/leds/leds-gpio.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/leds/leds-gpio.yaml b/Documentation/devicetree/bindings/leds/leds-gpio.yaml
index 7ad2baeda0b0..ae46a43e480f 100644
--- a/Documentation/devicetree/bindings/leds/leds-gpio.yaml
+++ b/Documentation/devicetree/bindings/leds/leds-gpio.yaml
@@ -21,7 +21,7 @@ properties:
patternProperties:
# The first form is preferred, but fall back to just 'led' anywhere in the
# node name to at least catch some child nodes.
- "(^led-[0-9a-f]$|led)":
+ "(^led-[0-9a-f][0-9a-f-]*$|led)":
type: object
$ref: common.yaml#
--
2.26.2
next reply other threads:[~2021-03-10 7:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 7:00 Rafał Miłecki [this message]
2021-03-12 7:44 ` [PATCH] dt-bindings: leds: leds-gpio: fix & extend node regex Marek Behun
2021-03-12 7:52 ` Rafał Miłecki
2021-03-12 8:23 ` Marek Behun
2021-03-12 9:12 ` Rafał Miłecki
2021-03-12 9:26 ` Marek Behun
2021-03-12 9:42 ` Rafał Miłecki
2021-03-16 22:31 ` Rob Herring
2021-03-16 22:44 ` Rafał Miłecki
2021-03-23 22:02 ` Rob Herring
2021-03-23 22:07 ` Rafał Miłecki
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=20210310070025.9150-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=f.fainelli@gmail.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafal@milecki.pl \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).