From: Lee Jones <lee.jones@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Marek Vasut <marek.vasut+renesas@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Subject: Re: [PATCH v3] dt-bindings: mfd: bd9571mwv: Convert to json-schema
Date: Wed, 24 Nov 2021 15:32:57 +0000 [thread overview]
Message-ID: <YZ5bKYZ0SF9xZU9F@google.com> (raw)
In-Reply-To: <76fdd209e6a2dada7ff50b8ad03eb14e7f3547a6.1635338031.git.geert+renesas@glider.be>
On Wed, 27 Oct 2021, Geert Uytterhoeven wrote:
> Convert the ROHM BD9571MWV/BD9574MWF Power Management Integrated Circuit
> (PMIC) Device Tree binding documentation to json-schema.
>
> Make the "regulators" subnode optional, as not all users describe the
> regulators.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Acked-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> ---
> I have listed Marek as the maintainer, as he wrote the original
> bindings. Marek: Please scream if this is inappropriate ;-)
>
> v3:
> - Add Acked-by,
>
> v2:
> - Add Reviewed-by.
> ---
> .../devicetree/bindings/mfd/bd9571mwv.txt | 69 ----------
> .../bindings/mfd/rohm,bd9571mwv.yaml | 127 ++++++++++++++++++
> 2 files changed, 127 insertions(+), 69 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/mfd/bd9571mwv.txt
> create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd9571mwv.yaml
Applied, thanks.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2021-11-24 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 12:34 [PATCH v3] dt-bindings: mfd: bd9571mwv: Convert to json-schema Geert Uytterhoeven
2021-11-24 15:32 ` 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=YZ5bKYZ0SF9xZU9F@google.com \
--to=lee.jones@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=matti.vaittinen@fi.rohmeurope.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).