From: Dave Penkler <dpenkler@gmail.com>
To: Ajith P V <ajithpv.linux@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: gpib: Resolve prefixing 0x with decimal
Date: Fri, 14 Feb 2025 13:04:25 +0100 [thread overview]
Message-ID: <Z68xSay4rBSecuMO@egonzo> (raw)
In-Reply-To: <20250206092815.3267-1-ajithpv.linux@gmail.com>
On Thu, Feb 06, 2025 at 02:58:15PM +0530, Ajith P V wrote:
> - pr_err() of hp82335_attach() in hp82335 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_82335/hp82335.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/gpib/hp_82335/hp82335.c b/drivers/staging/gpib/hp_82335/hp82335.c
> index 451d5dc6d340..6ce79b17a419 100644
> --- a/drivers/staging/gpib/hp_82335/hp82335.c
> +++ b/drivers/staging/gpib/hp_82335/hp82335.c
> @@ -274,7 +274,7 @@ static int hp82335_attach(gpib_board_t *board, const gpib_board_config_t *config
> case 0xfc000:
> break;
> default:
> - pr_err("hp82335: invalid base io address 0x%u\n", config->ibbase);
> + pr_err("hp82335: invalid base io address 0x%x\n", config->ibbase);
> return -EINVAL;
> }
> if (!request_mem_region(upper_iomem_base, hp82335_upper_iomem_size, "hp82335")) {
> --
> 2.43.0
>
Hi,
Thanks for your patch.
This patch is now superseded by
https://lore.kernel.org/linux-staging/20250214114708.28947-10-dpenkler@gmail.com/T/#u
which uses dev_err instead of pr_err and corrects the defective
prefix problem also.
-dave
next prev parent reply other threads:[~2025-02-14 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 9:28 [PATCH] staging: gpib: Resolve prefixing 0x with decimal Ajith P V
2025-02-14 12:04 ` Dave Penkler [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-04 13:51 Ajith P V
2025-02-04 14:06 ` Greg KH
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=Z68xSay4rBSecuMO@egonzo \
--to=dpenkler@gmail.com \
--cc=ajithpv.linux@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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