From: Herve Codina <herve.codina@bootlin.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org
Subject: Re: [PATCH net-next] wan: framer: pef2256: use %pe in print format
Date: Thu, 18 Sep 2025 16:08:34 +0200 [thread overview]
Message-ID: <20250918160834.47f746b9@bootlin.com> (raw)
In-Reply-To: <20250918134637.2226614-1-kuba@kernel.org>
Hi Jakub,
On Thu, 18 Sep 2025 06:46:37 -0700
Jakub Kicinski <kuba@kernel.org> wrote:
> New cocci check complains:
>
> drivers/net/wan/framer/pef2256/pef2256.c:733:3-10: WARNING: Consider using %pe to print PTR_ERR()
>
> Link: https://lore.kernel.org/1758192227-701925-1-git-send-email-tariqt@nvidia.com
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: herve.codina@bootlin.com
> ---
> drivers/net/wan/framer/pef2256/pef2256.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wan/framer/pef2256/pef2256.c b/drivers/net/wan/framer/pef2256/pef2256.c
> index 1e4c8e85d598..2a25cbd3f13b 100644
> --- a/drivers/net/wan/framer/pef2256/pef2256.c
> +++ b/drivers/net/wan/framer/pef2256/pef2256.c
> @@ -719,8 +719,8 @@ static int pef2256_probe(struct platform_device *pdev)
> pef2256->regmap = devm_regmap_init_mmio(&pdev->dev, iomem,
> &pef2256_regmap_config);
> if (IS_ERR(pef2256->regmap)) {
> - dev_err(&pdev->dev, "Failed to initialise Regmap (%ld)\n",
> - PTR_ERR(pef2256->regmap));
> + dev_err(&pdev->dev, "Failed to initialise Regmap (%pe)\n",
> + pef2256->regmap);
> return PTR_ERR(pef2256->regmap);
> }
>
Acked-by: Herve Codina <herve.codina@bootlin.com>
Best regards,
Hervé
next prev parent reply other threads:[~2025-09-18 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 13:46 [PATCH net-next] wan: framer: pef2256: use %pe in print format Jakub Kicinski
2025-09-18 14:08 ` Herve Codina [this message]
2025-09-19 15:10 ` patchwork-bot+netdevbpf
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=20250918160834.47f746b9@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).