From: Lee Jones <lee.jones@linaro.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Maxime Ripard <maxime@cerno.tech>,
Mark Rutland <mark.rutland@arm.com>,
Frank Rowand <frowand.list@gmail.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
devicetree@vger.kernel.org,
Andreas Kemnade <andreas@kemnade.info>
Subject: Re: [PATCH] dt-bindings: leds: lm3630a: Fix the example compilation
Date: Mon, 11 Nov 2019 09:56:58 +0000 [thread overview]
Message-ID: <20191111095658.GC3218@dell> (raw)
In-Reply-To: <CAL_Jsq+0X3jqO2B4o9Md1Vo5jO9cSvioeLNLrge9aoSsm-4aLg@mail.gmail.com>
On Tue, 05 Nov 2019, Rob Herring wrote:
> On Thu, Oct 31, 2019 at 8:48 AM Maxime Ripard <maxime@cerno.tech> wrote:
> >
> > 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(+)
>
> Lee already applied a fix. Though it's not in linux-next yet.
It is now.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2019-11-11 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 13:48 [PATCH] dt-bindings: leds: lm3630a: Fix the example compilation Maxime Ripard
2019-11-05 15:41 ` Rob Herring
2019-11-11 9:56 ` Lee Jones [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=20191111095658.GC3218@dell \
--to=lee.jones@linaro.org \
--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=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime@cerno.tech \
--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).