From: Maxime Ripard <maxime@cerno.tech>
To: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
lee.jones@linaro.org, daniel.thompson@linaro.org,
jingoohan1@gmail.com, jacek.anaszewski@gmail.com, pavel@ucw.cz,
dmurphy@ti.com
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
Maxime Ripard <maxime@cerno.tech>,
Andreas Kemnade <andreas@kemnade.info>
Subject: [PATCH] dt-bindings: leds: lm3630a: Fix the example compilation
Date: Thu, 31 Oct 2019 14:48:33 +0100 [thread overview]
Message-ID: <20191031134833.241303-1-maxime@cerno.tech> (raw)
Commit ae92365cdd75 ("dt-bindings: backlight: lm3630a: Add enable-gpios to
describe HWEN pin") introduced in the example a GPIO flag that isn't
declared anywhere, resulting in a compilation breakage when running the
validation tools. Add the proper define.
Cc: Andreas Kemnade <andreas@kemnade.info>
Cc: Lee Jones <lee.jones@linaro.org>
Fixes: ae92365cdd75 ("dt-bindings: backlight: lm3630a: Add enable-gpios to describe HWEN pin")
Signed-off-by: Maxime Ripard <maxime@cerno.tech>
---
.../devicetree/bindings/leds/backlight/lm3630a-backlight.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/leds/backlight/lm3630a-backlight.yaml b/Documentation/devicetree/bindings/leds/backlight/lm3630a-backlight.yaml
index c8470628fe02..72fc6f7ef90a 100644
--- a/Documentation/devicetree/bindings/leds/backlight/lm3630a-backlight.yaml
+++ b/Documentation/devicetree/bindings/leds/backlight/lm3630a-backlight.yaml
@@ -93,6 +93,8 @@ additionalProperties: false
examples:
- |
+ #include <dt-bindings/gpio/gpio.h>
+
i2c {
#address-cells = <1>;
#size-cells = <0>;
--
2.23.0
next reply other threads:[~2019-10-31 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 13:48 Maxime Ripard [this message]
2019-11-05 15:41 ` [PATCH] dt-bindings: leds: lm3630a: Fix the example compilation Rob Herring
2019-11-11 9:56 ` Lee Jones
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=20191031134833.241303-1-maxime@cerno.tech \
--to=maxime@cerno.tech \
--cc=andreas@kemnade.info \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=frowand.list@gmail.com \
--cc=jacek.anaszewski@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--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).