From: "Christian Kohlschütter" <christian@kohlschutter.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, lgirdwood@gmail.com
Subject: Re: [PATCH REBASE] regulator: core: Fix off-on-delay-us for always-on/boot-on regulators
Date: Tue, 19 Jul 2022 20:54:51 +0200 [thread overview]
Message-ID: <E5208D84-9501-4ADD-9747-817E8ADE75E7@kohlschutter.com> (raw)
In-Reply-To: <165825651232.448796.18429380716580437688.b4-ty@kernel.org>
Woohoo, my first patch — thanks a lot, Mark!
> Am 19.07.2022 um 20:48 schrieb Mark Brown <broonie@kernel.org>:
>
> On Tue, 19 Jul 2022 16:02:00 +0200, Christian Kohlschütter 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.
>>
>> This is caused by the "last_off" state not being initialized in this
>> case.
>>
>> [...]
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
>
> Thanks!
>
> [1/1] regulator: core: Fix off-on-delay-us for always-on/boot-on regulators
> commit: 218320fec29430438016f88dd4fbebfa1b95ad8d
>
> 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
next prev parent reply other threads:[~2022-07-19 18:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 11:30 [PATCH] " Christian Kohlschuetter
2022-07-17 11:39 ` Christian Kohlschütter
2022-07-17 11:49 ` Christian Kohlschütter
2022-07-18 12:36 ` Mark Brown
2022-07-18 17:24 ` [PATCH REBASE] " Christian Kohlschuetter
2022-07-19 13:57 ` [PATCH] " Mark Brown
2022-07-19 14:02 ` Christian Kohlschuetter
2022-07-19 14:02 ` [PATCH REBASE] " Christian Kohlschütter
2022-07-19 14:27 ` Mark Brown
2022-07-19 14:29 ` Mark Brown
2022-07-19 18:49 ` Christian Kohlschütter
2022-07-19 19:38 ` Mark Brown
2022-07-19 19:39 ` Christian Kohlschütter
2022-07-19 18:48 ` Mark Brown
2022-07-19 18:54 ` Christian Kohlschütter [this message]
2022-07-19 18:48 ` Mark Brown
2022-07-19 18:48 ` [PATCH] " Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E5208D84-9501-4ADD-9747-817E8ADE75E7@kohlschutter.com \
--to=christian@kohlschutter.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®