From: Mark Brown <broonie@kernel.org>
To: Christian Kohlschuetter <christian@kohlschuetter.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: core: Fix off-on-delay-us for always-on/boot-on regulators
Date: Tue, 19 Jul 2022 14:57:08 +0100 [thread overview]
Message-ID: <Yta4NGGYyZ6Doglr@sirena.org.uk> (raw)
In-Reply-To: <3270C618-E361-4BC1-B63A-917AE09DA60E@kohlschuetter.com>
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
On Mon, Jul 18, 2022 at 07:24:37PM +0200, Christian Kohlschuetter wrote:
> Signed-off-by: Christian Kohlschütter <christian@kohlschutter.com>
You have an umlaut in your signoff here but not in your e-mail address
which causes tooling to complain that there's a missing signoff - you
might get some complaints about this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-19 14:19 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 ` Mark Brown [this message]
2022-07-19 14:02 ` [PATCH] " 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
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=Yta4NGGYyZ6Doglr@sirena.org.uk \
--to=broonie@kernel.org \
--cc=christian@kohlschuetter.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.