Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 23 Sep 2020 20:00:37 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Liam Girdwood <lgirdwood@gmail.com>,
        Icenowy Zheng <icenowy@aosc.io>,
        Olliver Schinagl <oliver@schinagl.nl>,
        Chen-Yu Tsai <wens@csie.org>, Priit Laes <plaes@plaes.org>
Cc:     linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
In-Reply-To: <20200923005142.147135-1-icenowy@aosc.io>
References: <20200923005142.147135-1-icenowy@aosc.io>
Subject: Re: [PATCH] regulator: axp20x: fix LDO2/4 description
Message-Id: <160088763759.36155.1482459215779599768.b4-ty@kernel.org>
Precedence: bulk

On Wed, 23 Sep 2020 08:51:42 +0800, Icenowy Zheng wrote:
> Currently we wrongly set the mask of value of LDO2/4 both to the mask of
> LDO2, and the LDO4 voltage configuration is left untouched. This leads
> to conflict when LDO2/4 are both in use.
> 
> Fix this issue by setting different vsel_mask to both regulators.

Applied to

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

Thanks!

[1/1] regulator: axp20x: fix LDO2/4 description
      commit: fbb5a79d2fe7b01c6424fbbc04368373b1672d61

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