From: Timon Baetz <timon.baetz@protonmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Timon Baetz <timon.baetz@protonmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mfd: max8997: Replace 8998 with 8997
Date: Sun, 04 Apr 2021 14:22:55 +0000 [thread overview]
Message-ID: <20210404162225.213a9bee@focal-fossa> (raw)
In-Reply-To: <20210127073230.1583299-1-timon.baetz@protonmail.com>
On Wed, 27 Jan 2021 07:32:42 +0000, Timon Baetz wrote:
> The max8997 header is using "max8998" in some identifiers.
> Fix it by replacing 8998 with 8997 in enum and macro.
>
> Signed-off-by: Timon Baetz <timon.baetz@protonmail.com>
> ---
> v2: Fix commit message.
>
> include/linux/mfd/max8997.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/mfd/max8997.h b/include/linux/mfd/max8997.h
> index e955e2f0a2cc..6c98edcf4b0b 100644
> --- a/include/linux/mfd/max8997.h
> +++ b/include/linux/mfd/max8997.h
> @@ -14,13 +14,13 @@
> * others and b) it can be enabled simply by using MAX17042 driver.
> */
>
> -#ifndef __LINUX_MFD_MAX8998_H
> -#define __LINUX_MFD_MAX8998_H
> +#ifndef __LINUX_MFD_MAX8997_H
> +#define __LINUX_MFD_MAX8997_H
>
> #include <linux/regulator/consumer.h>
>
> /* MAX8997/8966 regulator IDs */
> -enum max8998_regulators {
> +enum max8997_regulators {
> MAX8997_LDO1 = 0,
> MAX8997_LDO2,
> MAX8997_LDO3,
> @@ -207,4 +207,4 @@ struct max8997_platform_data {
> struct max8997_led_platform_data *led_pdata;
> };
>
> -#endif /* __LINUX_MFD_MAX8998_H */
> +#endif /* __LINUX_MFD_MAX8997_H */
Hi, is there an issues with this patch?
next prev parent reply other threads:[~2021-04-04 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 7:32 [PATCH v2] mfd: max8997: Replace 8998 with 8997 Timon Baetz
2021-04-04 14:22 ` Timon Baetz [this message]
2021-04-07 9:40 ` Lee Jones
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=20210404162225.213a9bee@focal-fossa \
--to=timon.baetz@protonmail.com \
--cc=lee.jones@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).