From: Claudiu Beznea <claudiu.beznea@microchip.com>
To: <ludovic.desroches@microchip.com>, <linus.walleij@linaro.org>,
<nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: [PATCH 4/4] pinctrl: at91-pio4: use proper format specifier for unsigned int
Date: Thu, 2 Mar 2023 13:01:16 +0200 [thread overview]
Message-ID: <20230302110116.342486-5-claudiu.beznea@microchip.com> (raw)
In-Reply-To: <20230302110116.342486-1-claudiu.beznea@microchip.com>
Use %u instead of %d as line is unsigned int.
Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
---
drivers/pinctrl/pinctrl-at91-pio4.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-at91-pio4.c b/drivers/pinctrl/pinctrl-at91-pio4.c
index 783968182bc7..d6426367594e 100644
--- a/drivers/pinctrl/pinctrl-at91-pio4.c
+++ b/drivers/pinctrl/pinctrl-at91-pio4.c
@@ -1144,7 +1144,7 @@ static int atmel_pinctrl_probe(struct platform_device *pdev)
pin_desc[i].number = i;
/* Pin naming convention: P(bank_name)(bank_pin_number). */
- pin_desc[i].name = kasprintf(GFP_KERNEL, "P%c%d",
+ pin_desc[i].name = kasprintf(GFP_KERNEL, "P%c%u",
bank + 'A', line);
group->name = group_names[i] = pin_desc[i].name;
--
2.34.1
next prev parent reply other threads:[~2023-03-02 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 11:01 [PATCH 0/4] pinctrl: at91-pio4: few cleanups Claudiu Beznea
2023-03-02 11:01 ` [PATCH 1/4] pinctrl: at91-pio4: use devm_clk_get_enabled() Claudiu Beznea
2023-03-02 11:01 ` [PATCH 2/4] pinctrl: at91-pio4: use device_get_match_data() Claudiu Beznea
2023-03-02 11:01 ` [PATCH 3/4] pinctrl: at91-pio4: use dev_err_probe() Claudiu Beznea
2023-03-02 11:01 ` Claudiu Beznea [this message]
2023-03-07 13:14 ` [PATCH 0/4] pinctrl: at91-pio4: few cleanups Linus Walleij
2023-03-09 14:49 ` Claudiu.Beznea
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=20230302110116.342486-5-claudiu.beznea@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.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