From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Andrew Lunn <andrew@lunn.ch>,
Russell King <linux@armlinux.org.uk>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2 resend] arm: orion: use string choices helper
Date: Mon, 07 Jul 2025 16:56:31 +0200 [thread overview]
Message-ID: <87zfdgf3s0.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <877c0ou0xo.wl-kuninori.morimoto.gx@renesas.com>
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> writes:
> We can use string choices helper, let's use it.
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Applied on mvebu/arm
Thanks,
Gregory
> ---
> v1 -> v2
> - add commit message
> - add Reviewed-by
>
> arch/arm/plat-orion/gpio.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/plat-orion/gpio.c b/arch/arm/plat-orion/gpio.c
> index ca1bd764cfa5..6f09f65e3d95 100644
> --- a/arch/arm/plat-orion/gpio.c
> +++ b/arch/arm/plat-orion/gpio.c
> @@ -468,14 +468,14 @@ static void orion_gpio_dbg_show(struct seq_file *s, struct gpio_chip *chip)
>
> if (is_out) {
> seq_printf(s, " out %s %s\n",
> - out & msk ? "hi" : "lo",
> + str_hi_lo(out & msk),
> blink & msk ? "(blink )" : "");
> continue;
> }
>
> seq_printf(s, " in %s (act %s) - IRQ",
> - (data_in ^ in_pol) & msk ? "hi" : "lo",
> - in_pol & msk ? "lo" : "hi");
> + str_hi_lo((data_in ^ in_pol) & msk),
> + str_lo_hi(in_pol & msk));
> if (!((edg_msk | lvl_msk) & msk)) {
> seq_puts(s, " disabled\n");
> continue;
> --
> 2.43.0
>
--
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-07-07 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 2:47 [PATCH v2 resend] arm: orion: use string choices helper Kuninori Morimoto
2025-07-07 14:56 ` Gregory CLEMENT [this message]
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=87zfdgf3s0.fsf@BLaptop.bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@lunn.ch \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=sebastian.hesselbarth@gmail.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 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.