From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pawel Zalewski <pzalewski@thegoodpenguin.co.uk>
Cc: "Rob Herring (Arm)" <robh@kernel.org>,
Pavel Machek <pavel@kernel.org>,
Lucca Fachinetti <luccafachinetti@gmail.com>,
Conor Dooley <conor+dt@kernel.org>, Pavel Machek <pavel@ucw.cz>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Lee Jones <lee@kernel.org>,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: leds: is31fl32xx: convert the binding to yaml
Date: Fri, 18 Jul 2025 09:16:24 +0200 [thread overview]
Message-ID: <20250718-dangerous-smart-guppy-b8aa74@kuoka> (raw)
In-Reply-To: <CAA6zWZLyUt9X4+dAgYBVGqdNchasJorWhNH1O1Ti=UBO-J6q9g@mail.gmail.com>
On Fri, Jul 18, 2025 at 07:50:51AM +0100, Pawel Zalewski wrote:
> > If you already ran 'make dt_binding_check' and didn't see the above
> > error(s), then make sure 'yamllint' is installed and dt-schema is up to
> > date
>
> Hmm interesting, I did run it, have yamlint installed and see no
> errors. Will upgrade dtschema and try again.
Are you sure you tested patch #1 only?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-18 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 15:02 [PATCH v4 0/3] Add support for is31fl3236a LED controller Pawel Zalewski
2025-07-17 15:02 ` [PATCH v4 1/3] dt-bindings: leds: is31fl32xx: convert the binding to yaml Pawel Zalewski
2025-07-17 16:40 ` Rob Herring (Arm)
2025-07-18 6:50 ` Pawel Zalewski
2025-07-18 7:16 ` Krzysztof Kozlowski [this message]
2025-07-17 19:31 ` Rob Herring
2025-07-18 6:53 ` Pawel Zalewski
2025-07-17 15:02 ` [PATCH v4 2/3] dt-bindings: leds: issi,is31fl3236: add issi,22kHz-pwm property Pawel Zalewski
2025-07-17 15:02 ` [PATCH v4 3/3] leds/leds-is31fl32xx: add support for is31fl3236a Pawel Zalewski
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=20250718-dangerous-smart-guppy-b8aa74@kuoka \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=luccafachinetti@gmail.com \
--cc=pavel@kernel.org \
--cc=pavel@ucw.cz \
--cc=pzalewski@thegoodpenguin.co.uk \
--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