Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Mark Brown <broonie@kernel.org>
To:     hsin-hsiung.wang@mediatek.com, robh+dt@kernel.org,
        krzysztof.kozlowski+dt@linaro.org, lgirdwood@gmail.com,
        matthias.bgg@gmail.com, fparent@baylibre.com
Cc:     linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
In-Reply-To: <20220529154613.337559-1-fparent@baylibre.com>
References: <20220529154613.337559-1-fparent@baylibre.com>
Subject: Re: [PATCH] dt-bindings: regulator: mt6315-regulator: fix invalid allowed mode
Message-Id: <165408957615.3063838.14643425310508733291.b4-ty@kernel.org>
Date:   Wed, 01 Jun 2022 15:19:36 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Sun, 29 May 2022 17:46:13 +0200, Fabien Parent wrote:
> In the binding example, the regulator mode 4 is shown as a valid mode,
> but the driver actually only support mode 0 to 2:
> 
> This generates an error in dmesg when copy/pasting the binding example:
> [    0.306080] vbuck1: invalid regulator-allowed-modes element 4
> [    0.307290] vbuck2: invalid regulator-allowed-modes element 4
> 
> [...]

Applied to

   broonie/regulator.git for-linus

Thanks!

[1/1] dt-bindings: regulator: mt6315-regulator: fix invalid allowed mode
      commit: 28cbc2d4c54c09a427b18a1604740efb6b2cc2d6

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