From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pawel Zalewski <pzalewski@thegoodpenguin.co.uk>
Cc: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Pavel Machek <pavel@ucw.cz>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/3] leds/leds-is31fl32xx: add support for is31fl3236a
Date: Mon, 14 Jul 2025 11:35:52 +0200 [thread overview]
Message-ID: <2273eba8-1f98-4ec3-92f4-82a061e2336d@kernel.org> (raw)
In-Reply-To: <CAA6zWZKVnrPoutWpKQ+qzg5zNE-dhLxWBiuAoV5vf2qHfzv-LA@mail.gmail.com>
On 14/07/2025 11:09, Pawel Zalewski wrote:
>> Bindings go before the users (see submitting patches in DT).
>
> I think I was confused with point 7 stating that dt-binding should come
Point 7 speaks nothing about DT Bindings.
> last within a series and point 6 stating it is only regarding DTS files,
Neither point 6 says that it regards only DTS files.
> missed point 5 altogether... Thanks !
Are you sure you read correct and latest file?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-14 9:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 14:59 [PATCH v3 0/3] Add support for is31fl3236a LED controller Pawel Zalewski
2025-07-08 14:59 ` [PATCH v3 1/3] leds/leds-is31fl32xx: add support for is31fl3236a Pawel Zalewski
2025-07-09 8:12 ` Krzysztof Kozlowski
2025-07-14 9:09 ` Pawel Zalewski
2025-07-14 9:35 ` Krzysztof Kozlowski [this message]
2025-07-08 14:59 ` [PATCH v3 2/3] dt-bindings: leds: is31fl32xx: convert the binding to yaml Pawel Zalewski
2025-07-09 8:17 ` Krzysztof Kozlowski
2025-07-14 9:16 ` Pawel Zalewski
2025-07-14 9:36 ` Krzysztof Kozlowski
2025-07-09 8:18 ` Krzysztof Kozlowski
2025-07-08 14:59 ` [PATCH v3 3/3] dt-bindings: leds: issi,is31fl3236: add issi,22kHz-pwm property Pawel Zalewski
2025-07-09 8:19 ` Krzysztof Kozlowski
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=2273eba8-1f98-4ec3-92f4-82a061e2336d@kernel.org \
--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=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
all inboxes | Powered by JetHome®