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, 22 Jul 2020 01:57:25 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Liam Girdwood <lgirdwood@gmail.com>, Chen-Yu Tsai <wens@kernel.org>
Cc:     linux-arm-kernel@lists.infradead.org,
        Maxime Ripard <mripard@kernel.org>,
        Chen-Yu Tsai <wens@csie.org>, linux-kernel@vger.kernel.org
In-Reply-To: <20200720132809.26908-1-wens@kernel.org>
References: <20200720132809.26908-1-wens@kernel.org>
Subject: Re: [PATCH v3] regulator: gpio: Honor regulator-boot-on property
Message-Id: <159537943520.49645.14773067675144419268.b4-ty@kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, 20 Jul 2020 21:28:09 +0800, Chen-Yu Tsai wrote:
> When requesting the enable GPIO, the driver should do so with the
> correct output level matching some expected state. This is especially
> important if the regulator is a critical one, such as a supply for
> the boot CPU. This is currently done by checking for the enable-at-boot
> property, but this is not documented in the device tree binding, nor
> does it match the common regulator properties.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: gpio: Honor regulator-boot-on property
      commit: 3acff11cef1dece31cd29956f19181895996a7c5

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