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;
Content-Type: text/plain;
        charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
Subject: Re: [PATCH REBASE] regulator: core: Fix off-on-delay-us for
 always-on/boot-on regulators
From:   =?utf-8?Q?Christian_Kohlsch=C3=BCtter?= 
        <christian@kohlschutter.com>
In-Reply-To: <165825651232.448796.18429380716580437688.b4-ty@kernel.org>
Date:   Tue, 19 Jul 2022 20:54:51 +0200
Cc:     linux-kernel@vger.kernel.org, lgirdwood@gmail.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5208D84-9501-4ADD-9747-817E8ADE75E7@kohlschutter.com>
References: <E25D6465-6475-42B4-90EB-3D2C3CAF3B20@kohlschuetter.com>
 <YtVTyzLREdkzYiKS@sirena.org.uk>
 <3270C618-E361-4BC1-B63A-917AE09DA60E@kohlschuetter.com>
 <FAFD5B39-E9C4-47C7-ACF1-2A04CD59758D@kohlschutter.com>
 <165825651232.448796.18429380716580437688.b4-ty@kernel.org>
To:     Mark Brown <broonie@kernel.org>
Precedence: bulk

Woohoo, my first patch =E2=80=94 thanks a lot, Mark!

> Am 19.07.2022 um 20:48 schrieb Mark Brown <broonie@kernel.org>:
>=20
> On Tue, 19 Jul 2022 16:02:00 +0200, Christian Kohlsch=C3=BCtter wrote:
>> Regulators marked with "regulator-always-on" or "regulator-boot-on"
>> as well as an "off-on-delay-us", may run into cycling issues that are
>> hard to detect.
>>=20
>> This is caused by the "last_off" state not being initialized in this
>> case.
>>=20
>> [...]
>=20
> Applied to
>=20
>   =
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git =
for-next
>=20
> Thanks!
>=20
> [1/1] regulator: core: Fix off-on-delay-us for always-on/boot-on =
regulators
>      commit: 218320fec29430438016f88dd4fbebfa1b95ad8d
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>=20
> Thanks,
> Mark