Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     jic23@kernel.org, lars@metafoo.de, bjorn.andersson@linaro.org,
        lee.jones@linaro.org, lgirdwood@gmail.com,
        linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
        linux-arm-msm@vger.kernel.org, linux-iio@vger.kernel.org,
        krzysztof.kozlowski+dt@linaro.org, konrad.dybcio@somainline.org,
        linus.walleij@linaro.org, agross@kernel.org, robimarko@gmail.com,
        robh+dt@kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <20220704212402.1715182-1-robimarko@gmail.com>
References: <20220704212402.1715182-1-robimarko@gmail.com>
Subject: Re: (subset) [PATCH v6 01/12] dt-bindings: mfd: qcom-spmi-pmic: add support for PMP8074
Message-Id: <165756665871.1166849.13520807599525950221.b4-ty@kernel.org>
Date:   Mon, 11 Jul 2022 20:10:58 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 4 Jul 2022 23:23:51 +0200, Robert Marko wrote:
> Document compatible for the PMP8074 PMIC.
> 
> I planned to convert the bindings to dtschema, but there is already a
> patch to do so [1].
> I will make a patch to add the compatible to dtschema once it gets
> accepted.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[03/12] dt-bindings: regulator: qcom,spmi-regulator: Convert to dtschema
        commit: 0b3bbd7646b03920e81efa376dee08f5b288c05e
[04/12] regulator: qcom_spmi: add support for HT_P150
        commit: 00f6ebbd0177a4cb15b353bbd4eaee6372fdbbc2
[05/12] regulator: qcom_spmi: add support for HT_P600
        commit: 3d04ae8e3e916bc298b674613565d5b26cf1054a
[06/12] dt-bindings: regulator: qcom,spmi-regulator: add PMP8074 PMIC
        commit: 044750573903595765fa52ba9e1aadc397d591df
[07/12] regulator: qcom_spmi: add support for PMP8074 regulators
        commit: 34ceb6a6ef87cda7629fd4ebe0074d9b5c7613d9

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark