From: Mark Brown <broonie@kernel.org>
To: "Christian Kohlschütter" <christian@kohlschutter.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH REBASE] regulator: core: Fix off-on-delay-us for always-on/boot-on regulators
Date: Tue, 19 Jul 2022 20:38:09 +0100 [thread overview]
Message-ID: <YtcIIaFeVIzor/jD@sirena.org.uk> (raw)
In-Reply-To: <20220719184943.1566-1-christian@kohlschutter.com>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Tue, Jul 19, 2022 at 06:49:44PM +0000, 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.
I think this already got applied, I had another go at persuading things
to cope which seemed to work - not 100% sure what was going on, git
seemed less forgiving than raw patch here. It didn't look like a
rebasing issue, it looked like the umlaut was upsetting git. Should be
commit 218320fec29430438016f88dd4fbebfa1b95ad8d in my tree.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-19 19:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 11:30 [PATCH] regulator: core: Fix off-on-delay-us for always-on/boot-on regulators Christian Kohlschuetter
2022-07-17 11:39 ` Christian Kohlschütter
2022-07-17 11:49 ` Christian Kohlschütter
2022-07-17 11:49 ` 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 [this message]
2022-07-19 19:39 ` Christian Kohlschütter
2022-07-19 18:48 ` Mark Brown
2022-07-19 18:54 ` Christian Kohlschütter
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=YtcIIaFeVIzor/jD@sirena.org.uk \
--to=broonie@kernel.org \
--cc=christian@kohlschutter.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.