From: Damien Le Moal <dlemoal@kernel.org>
To: zhangjiao2 <zhangjiao2@cmss.chinamobile.com>
Cc: linus.walleij@linaro.org, linux-riscv@lists.infradead.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: k210: Modify the wrong "#undef"
Date: Wed, 13 Nov 2024 13:41:36 +0900 [thread overview]
Message-ID: <deafaca0-63e0-4c5a-8d34-21567f78a5cb@kernel.org> (raw)
In-Reply-To: <20241113012029.3204-1-zhangjiao2@cmss.chinamobile.com>
On 11/13/24 10:20, zhangjiao2 wrote:
> From: zhang jiao <zhangjiao2@cmss.chinamobile.com>
>
> Here shuld be undef "K210_PC_DEFAULT", not "DEFAULT".
Here ? Please be specific.
Also:
s/shuld/must
So something like:
The definition of the array k210_pinconf_mode_id_to_mode is done using the
temporary macro K210_PC_DEFAULT. When this macro is not needed anymore and its
definition removed, make sure to use its name in the #undef statement instead of
the incorrect "DEFAULT" name.
>
> Signed-off-by: zhang jiao <zhangjiao2@cmss.chinamobile.com>
This needs a Fixes tag as well.
> ---
> drivers/pinctrl/pinctrl-k210.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/pinctrl-k210.c b/drivers/pinctrl/pinctrl-k210.c
> index caf20215aaba..eddb01796a83 100644
> --- a/drivers/pinctrl/pinctrl-k210.c
> +++ b/drivers/pinctrl/pinctrl-k210.c
> @@ -181,7 +181,7 @@ static const u32 k210_pinconf_mode_id_to_mode[] = {
> [K210_PC_DEFAULT_INT13] = K210_PC_MODE_IN | K210_PC_PU,
> };
>
> -#undef DEFAULT
> +#undef K210_PC_DEFAULT
>
> /*
> * Pin functions configuration information.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-11-13 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 1:20 [PATCH] pinctrl: k210: Modify the wrong "#undef" zhangjiao2
2024-11-13 4:41 ` Damien Le Moal [this message]
2024-12-11 22:32 ` patchwork-bot+linux-riscv
2024-12-20 12:36 ` Linus Walleij
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=deafaca0-63e0-4c5a-8d34-21567f78a5cb@kernel.org \
--to=dlemoal@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=zhangjiao2@cmss.chinamobile.com \
/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