From: Geert Uytterhoeven <geert@linux-m68k.org>
To: liujing <liujing@cmss.chinamobile.com>
Cc: ysato@users.sourceforge.jp, dalias@libc.org,
glaubitz@physik.fu-berlin.de, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: pci: Fix the wrong format specifier
Date: Wed, 4 Dec 2024 13:35:12 +0100 [thread overview]
Message-ID: <CAMuHMdXu04CFhkc3E=cA9wi_eigc1q88azb8k5N4UeyMAgKOkw@mail.gmail.com> (raw)
In-Reply-To: <20241204110706.6776-1-liujing@cmss.chinamobile.com>
Hi Liujing,
On Wed, Dec 4, 2024 at 12:10 PM liujing <liujing@cmss.chinamobile.com> wrote:
> Make a minor change to eliminate a static checker warning. The type
> of port->index is unsigned int, so the correct format specifier should be
> %u instead of %d.
>
> Signed-off-by: liujing <liujing@cmss.chinamobile.com>
Thanks for your patch!
> --- a/arch/sh/drivers/pci/pcie-sh7786.c
> +++ b/arch/sh/drivers/pci/pcie-sh7786.c
> @@ -219,7 +219,7 @@ static int __init pcie_clk_init(struct sh7786_pcie_port *port)
> * on. clock lookups don't help us much at this point, since no
> * dev_id is available this early. Lame.
> */
> - snprintf(fclk_name, sizeof(fclk_name), "pcie%d_fck", port->index);
> + snprintf(fclk_name, sizeof(fclk_name), "pcie%u_fck", port->index);
>
> port->fclk = clk_get(NULL, fclk_name);
> if (IS_ERR(port->fclk)) {
LGTM, but there are several more cases to fix in this file.
Please fix all of them in a single patch.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-12-04 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 11:07 [PATCH] sh: pci: Fix the wrong format specifier liujing
2024-12-04 12:35 ` Geert Uytterhoeven [this message]
2025-01-30 8:24 ` John Paul Adrian Glaubitz
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='CAMuHMdXu04CFhkc3E=cA9wi_eigc1q88azb8k5N4UeyMAgKOkw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=liujing@cmss.chinamobile.com \
--cc=ysato@users.sourceforge.jp \
/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).