From: Jeff LaBundy <jeff@labundy.com>
To: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Alexander Dahl <ada@thorsis.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-amlogic@lists.infradead.org, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v9 1/4] dt-bindings: mfd: Fix schema warnings for pwm-leds
Date: Sun, 17 Jan 2021 22:02:54 -0600 [thread overview]
Message-ID: <20210118040254.GA7479@labundy.com> (raw)
In-Reply-To: <20210115094238.s36rrgmpq63a622p@falbala.internal.home.lespocky.de>
Hi Alexander,
Thanks again for your work on this.
On Fri, Jan 15, 2021 at 10:42:39AM +0100, Alexander Dahl wrote:
> Hello Jeff,
>
> On Thu, Jan 14, 2021 at 09:50:50PM -0600, Jeff LaBundy wrote:
> > On Thu, Jan 14, 2021 at 10:03:12AM +0000, Lee Jones wrote:
> > > On Mon, 28 Dec 2020, Alexander Dahl wrote:
> > >
> > > > The node names for devices using the pwm-leds driver follow a certain
> > > > naming scheme (now). Parent node name is not enforced, but recommended
> > > > by DT project.
> > > >
> > > > DTC Documentation/devicetree/bindings/mfd/iqs62x.example.dt.yaml
> > > > CHECK Documentation/devicetree/bindings/mfd/iqs62x.example.dt.yaml
> > > > /home/alex/build/linux/Documentation/devicetree/bindings/mfd/iqs62x.example.dt.yaml: pwmleds: 'panel' does not match any of the regexes: '^led(-[0-9a-f]+)?$', 'pinctrl-[0-9]+'
> > > > From schema: /home/alex/src/linux/leds/Documentation/devicetree/bindings/leds/leds-pwm.yaml
> > > >
> > > > Signed-off-by: Alexander Dahl <post@lespocky.de>
> > > > Acked-by: Jeff LaBundy <jeff@labundy.com>
> > > > Acked-by: Rob Herring <robh@kernel.org>
> > > > ---
> > > >
> > > > Notes:
> > > > v8 -> v9:
> > > > * added forgotten Acked-by (Jeff LaBundy)
> > > > * rebased on v5.11-rc1
> > > >
> > > > v7 -> v8:
> > > > * rebased on recent pavel/for-next (post v5.10-rc1)
> > > > * added Acked-by (Rob Herring)
> > > >
> > > > v6 -> v7:
> > > > * added warning message to commit message (Krzysztof Kozlowski)
> > > >
> > > > v6:
> > > > * added this patch to series
> > > >
> > > > Documentation/devicetree/bindings/mfd/iqs62x.yaml | 5 +++--
> > > > 1 file changed, 3 insertions(+), 2 deletions(-)
> > >
> > > Failed to apply:
> > >
> > > Applying: dt-bindings: mfd: Fix schema warnings for pwm-leds
> > > Using index info to reconstruct a base tree...
> > > M Documentation/devicetree/bindings/mfd/iqs62x.yaml
> > > /home/lee/projects/linux/kernel/.git/worktrees/mfd/rebase-apply/patch:34: indent with spaces.
> > > led-1 {
> > > /home/lee/projects/linux/kernel/.git/worktrees/mfd/rebase-apply/patch:35: indent with spaces.
> > > label = "panel";
> > > warning: 2 lines add whitespace errors.
> > > Falling back to patching base and 3-way merge...
> > > Auto-merging Documentation/devicetree/bindings/mfd/iqs62x.yaml
> > > CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/mfd/iqs62x.yaml
> > > Recorded preimage for 'Documentation/devicetree/bindings/mfd/iqs62x.yaml'
> >
> > It looks like the following patch already beat this to the punch:
> >
> > 8237e8382498 ("dt-bindings: mfd: Correct the node name of the panel LED")
>
> Which tree is that commit on? This one?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/
That's correct.
>
> > That patch does not retain the LED's label or rename the parent node to
> > led-controller, however. The label hardly matters for this example, but
> > perhaps we still want the parent node change to follow leds-pwm.yaml.
>
> Should I rework the patch then to have that change only?
That seems like a reasonable compromise.
>
> Greets
> Alex
>
> --
> /"\ ASCII RIBBON | »With the first link, the chain is forged. The first
> \ / CAMPAIGN | speech censured, the first thought forbidden, the
> X AGAINST | first freedom denied, chains us all irrevocably.«
> / \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
Kind regards,
Jeff LaBundy
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-18 4:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 16:32 [PATCH v9 0/4] leds: pwm: Make automatic labels work Alexander Dahl
2020-12-28 16:32 ` [PATCH v9 1/4] dt-bindings: mfd: Fix schema warnings for pwm-leds Alexander Dahl
2020-12-30 18:54 ` Pavel Machek
2020-12-31 8:33 ` Lee Jones
2020-12-31 9:39 ` Pavel Machek
2020-12-31 12:18 ` Lee Jones
2021-01-14 10:03 ` Lee Jones
2021-01-15 3:50 ` Jeff LaBundy
2021-01-15 9:42 ` Alexander Dahl
2021-01-18 4:02 ` Jeff LaBundy [this message]
2020-12-28 16:32 ` [PATCH v9 2/4] ARM: dts: berlin: " Alexander Dahl
2020-12-29 2:24 ` Jisheng Zhang
2020-12-28 16:32 ` [PATCH v9 3/4] ARM: dts: stm32: " Alexander Dahl
2021-01-14 16:07 ` Alexandre TORGUE
2020-12-28 16:32 ` [PATCH v9 4/4] arm64: dts: meson: " Alexander Dahl
2021-01-04 16:13 ` Kevin Hilman
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=20210118040254.GA7479@labundy.com \
--to=jeff@labundy.com \
--cc=ada@thorsis.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).