From: Greg KH <gregkh@linuxfoundation.org>
To: Ajith P V <ajithpv.linux@gmail.com>
Cc: dpenkler@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: gpib: Resolve prefixing 0x with decimal
Date: Tue, 4 Feb 2025 15:06:20 +0100 [thread overview]
Message-ID: <2025020401-unloved-judiciary-2fb8@gregkh> (raw)
In-Reply-To: <20250204135131.3094-1-ajithpv.linux@gmail.com>
On Tue, Feb 04, 2025 at 07:21:31PM +0530, Ajith P V wrote:
> - pr_info() of hp_82341_attach() in hp_82341 uses 0x%u which is defective.
> - The iobase is of u32 and correct prefix is 0x%x.
> - This error reported by checkpatch with below message:
> ERROR: Prefixing 0x with decimal output is defective.
>
> Signed-off-by: Ajith P V <ajithpv.linux@gmail.com>
> ---
> drivers/staging/gpib/hp_82341/hp_82341.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/gpib/hp_82341/hp_82341.c b/drivers/staging/gpib/hp_82341/hp_82341.c
> index 800f99c05566..740c450914dc 100644
> --- a/drivers/staging/gpib/hp_82341/hp_82341.c
> +++ b/drivers/staging/gpib/hp_82341/hp_82341.c
> @@ -723,7 +723,7 @@ static int hp_82341_attach(gpib_board_t *board, const gpib_board_config_t *confi
> hp_priv->hw_version = HW_VERSION_82341C;
> hp_priv->io_region_offset = 0x400;
> }
> - pr_info("hp_82341: base io 0x%u\n", iobase);
> + pr_info("hp_82341: base io 0x%x\n", iobase);
When drivers work properly, they are quiet. Lines like this should just
be removed.
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-04 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 13:51 [PATCH] staging: gpib: Resolve prefixing 0x with decimal Ajith P V
2025-02-04 14:06 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-06 9:28 Ajith P V
2025-02-14 12:04 ` Dave Penkler
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=2025020401-unloved-judiciary-2fb8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ajithpv.linux@gmail.com \
--cc=dpenkler@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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