From: Lee Jones <lee.jones@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] mfd/regulator: dt-bindings: max77686: convert to dtschema
Date: Thu, 21 Oct 2021 12:47:52 +0100 [thread overview]
Message-ID: <YXFTaCETelkSOeu+@google.com> (raw)
In-Reply-To: <85c56cfb-64d9-a840-c2e4-eea47461188d@canonical.com>
On Thu, 21 Oct 2021, Krzysztof Kozlowski wrote:
> On 21/10/2021 12:03, Lee Jones wrote:
> > On Fri, 08 Oct 2021, Krzysztof Kozlowski wrote:
> >
> >> Hi,
> >>
> >> Convert Maxim MAX77686 bindings to dtschema. The MFD patch (2/2)
> >> depends on regulator, so this should go via one tree, for example MFD or DT.
> >>
> >> Changes since v1:
> >> =================
> >> See individual patches.
> >>
> >> Clock bindings
> >> ==============
> >> Existing Documentation/devicetree/bindings/clock/maxim,max77686.txt are
> >> left untouched. The file is still used/referenced by other Maxim
> >> devices: MAX77620 and MAX77802.
> >>
> >> Best regards,
> >> Krzysztof
> >>
> >> Krzysztof Kozlowski (2):
> >> regulator: dt-bindings: maxim,max77686: convert to dtschema
> >> dt-bindings: mfd: maxim,max77686: convert to dtschema
> >>
> >> .../devicetree/bindings/mfd/max77686.txt | 26 ----
> >> .../bindings/mfd/maxim,max77686.yaml | 132 ++++++++++++++++++
> >> .../bindings/regulator/max77686.txt | 71 ----------
> >> .../bindings/regulator/maxim,max77686.yaml | 83 +++++++++++
> >> MAINTAINERS | 2 +-
> >> 5 files changed, 216 insertions(+), 98 deletions(-)
> >> delete mode 100644 Documentation/devicetree/bindings/mfd/max77686.txt
> >> create mode 100644 Documentation/devicetree/bindings/mfd/maxim,max77686.yaml
> >> delete mode 100644 Documentation/devicetree/bindings/regulator/max77686.txt
> >> create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77686.yaml
> >
> > Does this need a PR too?
>
> No, I hope not. The regulator patch was acked by Mark and Rob, so you
> can freely take both of these. I am not aware of any conflicts or other
> dependencies.
Acks do sometimes need PRs to be reciprocated. Just need to make sure.
Mark, do you need a PR if I take this in via MFD?
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2021-10-21 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 12:35 [PATCH v2 0/2] mfd/regulator: dt-bindings: max77686: convert to dtschema Krzysztof Kozlowski
2021-10-08 12:35 ` [PATCH v2 1/2] regulator: dt-bindings: maxim,max77686: " Krzysztof Kozlowski
2021-10-08 20:40 ` Rob Herring
2021-10-08 12:35 ` [PATCH v2 2/2] dt-bindings: mfd: " Krzysztof Kozlowski
2021-10-21 10:03 ` [PATCH v2 0/2] mfd/regulator: dt-bindings: max77686: " Lee Jones
2021-10-21 10:12 ` Krzysztof Kozlowski
2021-10-21 11:47 ` Lee Jones [this message]
2021-11-24 15:31 ` Lee Jones
2021-11-24 18:32 ` 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=YXFTaCETelkSOeu+@google.com \
--to=lee.jones@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.