From: Jeff Layton <jlayton@kernel.org>
To: Qasim Ijaz <qasdev00@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: use %ld format specifier for PTR_ERR in pr_warn
Date: Sun, 13 Apr 2025 06:59:49 -0400 [thread overview]
Message-ID: <3fb6238636b4e20172a357a043001426e7fa34c2.camel@kernel.org> (raw)
In-Reply-To: <20250412225528.12667-1-qasdev00@gmail.com>
On Sat, 2025-04-12 at 23:55 +0100, Qasim Ijaz wrote:
> PTR_ERR yields type long, so use %ld format specifier in pr_warn.
>
> Fixes: 193510c95215 ("net: add debugfs files for showing netns refcount tracking info")
> Signed-off-by: Qasim Ijaz <qasdev00@gmail.com>
> ---
> net/core/net_namespace.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/core/net_namespace.c b/net/core/net_namespace.c
> index f47b9f10af24..a419a3aa57a6 100644
> --- a/net/core/net_namespace.c
> +++ b/net/core/net_namespace.c
> @@ -1652,7 +1652,7 @@ static int __init ns_debug_init(void)
> if (ref_tracker_debug_dir) {
> ns_ref_tracker_dir = debugfs_create_dir("net_ns", ref_tracker_debug_dir);
> if (IS_ERR(ns_ref_tracker_dir)) {
> - pr_warn("net: unable to create ref_tracker/net_ns directory: %d\n",
> + pr_warn("net: unable to create ref_tracker/net_ns directory: %ld\n",
> PTR_ERR(ns_ref_tracker_dir));
> goto out;
> }
Thanks, that will silence a potential compiler warning. This is not
merged yet, but I'll make sure to incorporate this change in the next
version.
FWIW, I'm planning to put together a v3 that will require less
involvement with net/ code, so most of these bits will probably get
deleted anyway.
Cheers!
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2025-04-13 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 22:55 [PATCH] net: use %ld format specifier for PTR_ERR in pr_warn Qasim Ijaz
2025-04-12 23:28 ` Kuniyuki Iwashima
2025-04-13 2:07 ` Nathan Chancellor
2025-04-13 10:56 ` Qasim Ijaz
2025-04-13 10:59 ` Jeff Layton [this message]
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=3fb6238636b4e20172a357a043001426e7fa34c2.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qasdev00@gmail.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).