linux-kernel - Re: [PATCH v2 0/2] mfd/regulator: dt-bindings: max77686: convert to dtschema

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 21 Oct 2021 12:47:52 +0100
From:   Lee Jones <lee.jones@...aro.org>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Chanwoo Choi <cw00.choi@...sung.com>,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] mfd/regulator: dt-bindings: max77686: convert to
 dtschema

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