devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [PATCH v2 0/5] mfd/extcon/regulators: max77843: add dtschema/bindings
Date: Mon, 7 Feb 2022 09:33:04 +0000	[thread overview]
Message-ID: <YgDnUNCNCO+JLyHU@google.com> (raw)
In-Reply-To: <1bebedb9-644f-783d-492c-84a5de91720d@canonical.com>

On Sun, 06 Feb 2022, Krzysztof Kozlowski wrote:

> On 11/01/2022 18:48, Krzysztof Kozlowski wrote:
> > Hi,
> > 
> > The max77843 shares some parts with max77693 but it lacked bindings.  All
> > its compatibles were undocumented.  Add basic bindings for max77843,
> > matching existing devicetree.  These are not complete bindings, but
> > rather reverse-engineered to match current state.
> > 
> > I do not have access to device with MAX77843, so if anyone else
> > volunteers to be the bindings maintainer, please join.
> > 
> > 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.
> > 3. extcon: Use absolute path to schemas.
> > 
> > Dependencies
> > ============
> > 1. Patch 1/5 (dts): 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. The patch 4/5 (mfd bindings) depends on regulator and extcon, so they
> >    should come together (2+3+4+5).
> > 
> Dear Lee,
> 
> This patchset was reviewed and there are no outstanding issues. Could
> you pick up patches 2-5 (skipping DTS patch) via MFD tree?

Are the subsystem maintainers not going to review/ack?

-- 
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2022-02-07  9:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 17:48 [PATCH v2 0/5] mfd/extcon/regulators: max77843: add dtschema/bindings Krzysztof Kozlowski
2022-01-11 17:48 ` [PATCH v2 1/5] arm64: dts: exynos: Align MAX77843 nodes with dtschema on TM2 Krzysztof Kozlowski
2022-01-23 17:10   ` (subset) " Krzysztof Kozlowski
2022-01-11 17:48 ` [PATCH v2 2/5] dt-bindings: extcon: maxim,max77843: add MAX77843 bindings Krzysztof Kozlowski
2022-03-07  9:08   ` Lee Jones
2022-03-09 21:03   ` Rob Herring
2022-03-10  7:27     ` Krzysztof Kozlowski
2022-01-11 17:48 ` [PATCH v2 3/5] regulator: dt-bindings: " Krzysztof Kozlowski
2022-01-11 22:21   ` Rob Herring
2022-02-11 11:59   ` Mark Brown
2022-03-07  9:11   ` Lee Jones
2022-01-11 17:48 ` [PATCH v2 4/5] dt-bindings: mfd: " Krzysztof Kozlowski
2022-03-07  9:13   ` Lee Jones
2022-01-11 17:48 ` [PATCH v2 5/5] MAINTAINERS: mfd: cover MAX77843 by Maxim PMIC/MUIC for Exynos boards entry Krzysztof Kozlowski
2022-03-07  9:16   ` Lee Jones
2022-02-06 17:39 ` [PATCH v2 0/5] mfd/extcon/regulators: max77843: add dtschema/bindings Krzysztof Kozlowski
2022-02-07  9:33   ` Lee Jones [this message]
2022-02-07  9:47     ` Krzysztof Kozlowski
2022-02-07 10:11       ` Lee Jones
2022-02-07 16:25       ` Mark Brown
2022-03-07 13:04 ` [GIT PULL] Immutable branch between MFD, SPI and DT due for the v5.18 merge window 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=YgDnUNCNCO+JLyHU@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-samsung-soc@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --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 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).