From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Steve Twiss <stwiss.opensource@diasemi.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH] dt-bindings: mfd: dlg,da9063: add missing regulator patterns
Date: Sun, 25 Sep 2022 10:02:11 +0100 [thread overview]
Message-ID: <7605FF4F-896B-42A0-8A8F-4540365F9394@kernel.org> (raw)
In-Reply-To: <e20375a8-4496-315e-67f8-feb8ddfd6d3e@linaro.org>
On 17 September 2022 17:44:06 IST, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
>On 16/09/2022 20:00, Conor Dooley wrote:
>> From: Conor Dooley <conor.dooley@microchip.com>
>>
>> Commit 5621d3977e29 ("dt-bindings: mfd: Add missing (unevaluated|
>> additional)Properties on child nodes") exposed a flaw in the original
>> binding, where "merged" versions of some regulators were missing,
>> leading to warnings on the HiFive Unmatched Devicetree.
>>
>> Add the missing patterns (and merge some of the trivial ones).
>>
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>> ---
>> I opted not to include a fixes tag for the conversion since it just
>> converted what was already there. I figured the original text binding
>> is just incomplete rather than "broken", but if you don't agree the
>> fixes tag would be:
>> Fixes: c7f15d43a5c5 ("mfd: devicetree: Add bindings for DA9063")
>>
>> Documentation/devicetree/bindings/mfd/dlg,da9063.yaml | 2 +-
>
>
>Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
Hey Lee,
Is it too late to pick this up for 6.1?
It's the last remaining dt warning in for riscv.
Thanks,
Conor
next prev parent reply other threads:[~2022-09-25 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 19:00 [PATCH] dt-bindings: mfd: dlg,da9063: add missing regulator patterns Conor Dooley
2022-09-17 16:44 ` Krzysztof Kozlowski
2022-09-25 9:02 ` Conor Dooley [this message]
2022-09-26 7:44 ` 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=7605FF4F-896B-42A0-8A8F-4540365F9394@kernel.org \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stwiss.opensource@diasemi.com \
/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).