Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Mark Brown <broonie@kernel.org>
To:     nfraprado@collabora.com
Cc:     matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
        hsin-hsiung.wang@mediatek.com, krzysztof.kozlowski+dt@linaro.org,
        robh+dt@kernel.org, kernel@collabora.com,
        linux-mediatek@lists.infradead.org, lgirdwood@gmail.com,
        linux-arm-kernel@lists.infradead.org
In-Reply-To: <20220429201325.2205799-1-nfraprado@collabora.com>
References: <20220429201325.2205799-1-nfraprado@collabora.com>
Subject: Re: [PATCH] dt-bindings: regulator: mt6315: Enforce regulator-compatible, not name
Message-Id: <165169662791.1744767.17732308037249256443.b4-ty@kernel.org>
Date:   Wed, 04 May 2022 21:37:07 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 29 Apr 2022 16:13:24 -0400, Nícolas F. R. A. Prado wrote:
> The MT6315 PMIC dt-binding should enforce that one of the valid
> regulator-compatible is set in each regulator node. However it was
> mistakenly matching against regulator-name instead.
> 
> Fix the typo. This not only fixes the compatible verification, but also
> lifts the regulator-name restriction, so that more meaningful names can
> be set for each platform.
> 
> [...]

Applied to

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

Thanks!

[1/1] dt-bindings: regulator: mt6315: Enforce regulator-compatible, not name
      commit: 6d435a94ba5bb4f2ad381c0828fbae89c66b50fe

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