From: Lee Jones <lee.jones@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Mark Brown <broonie@kernel.org>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [PATCH v2 0/4] mfd/power/regulators: dt-bindings: max14577: convert to dtschema
Date: Mon, 7 Feb 2022 09:34:13 +0000 [thread overview]
Message-ID: <YgDnlWKO6/BTxZh2@google.com> (raw)
In-Reply-To: <73bad620-97eb-a734-cbc8-6f001d04c18a@canonical.com>
On Sun, 06 Feb 2022, Krzysztof Kozlowski wrote:
> On 11/01/2022 18:43, Krzysztof Kozlowski wrote:
> > Hi,
> >
> > Changes since v1
> > ================
> > 1. MFD: Use absolute path to schemas
> > 2. Regulator: mention all allowed properties,
> > additionalProperties=false, add min/max values for voltages and
> > current, don't use patternProperties when not needed.
> >
> > Dependencies
> > ============
> > 1. DTS patch 1/4: nothing depends on it, sending here so Rob's automatic
> > checker won't complain about DTS.
> > I will take it via Samsung SoC tree.
> >
> > 2. Final MFD patch (4/4) depends on regulator and power, so the last
> > patches (2+3+4) should go via same tree.
> >
> Dear Lee,
>
> This patchset was reviewed and there are no outstanding issues. Could
> you pick up patches 2-4 (skipping DTS patch) via MFD tree?
Nothing from Mark?
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2022-02-07 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 17:43 [PATCH v2 0/4] mfd/power/regulators: dt-bindings: max14577: convert to dtschema Krzysztof Kozlowski
2022-01-11 17:43 ` [PATCH v2 1/4] ARM: dts: exynos: Align MAX77836 nodes with dtschema on Monk and Rinato Krzysztof Kozlowski
2022-01-23 17:10 ` (subset) " Krzysztof Kozlowski
2022-01-11 17:43 ` [PATCH v2 2/4] dt-bindings: power: supply: maxim,max14577: convert to dtschema Krzysztof Kozlowski
2022-01-12 11:29 ` Sebastian Reichel
2022-02-14 14:17 ` Lee Jones
2022-02-14 16:37 ` Sebastian Reichel
2022-01-11 17:43 ` [PATCH v2 3/4] regulator: dt-bindings: " Krzysztof Kozlowski
2022-01-11 22:21 ` Rob Herring
2022-02-14 16:43 ` Mark Brown
2022-02-14 16:54 ` Krzysztof Kozlowski
2022-02-14 16:59 ` Mark Brown
2022-01-11 17:43 ` [PATCH v2 4/4] dt-bindings: mfd: " Krzysztof Kozlowski
2022-02-06 17:39 ` [PATCH v2 0/4] mfd/power/regulators: dt-bindings: max14577: " Krzysztof Kozlowski
2022-02-07 9:34 ` Lee Jones [this message]
2022-02-07 9:43 ` Krzysztof Kozlowski
2022-02-07 10:11 ` 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=YgDnlWKO6/BTxZh2@google.com \
--to=lee.jones@linaro.org \
--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-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@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).