From: Brendan Jackman <jackmanb@google.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Stanislaw Gruszka <stf_xl@wp.pl>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Allison Henderson <allison.henderson@oracle.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, kasan-dev@googlegroups.com,
linux-mm@kvack.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
Brendan Jackman <jackmanb@google.com>
Subject: [PATCH v2 4/4] net/rds: Use special gfp_t format specifier
Date: Thu, 26 Mar 2026 12:32:00 +0000 [thread overview]
Message-ID: <20260326-gfp64-v2-4-d916021cecdf@google.com> (raw)
In-Reply-To: <20260326-gfp64-v2-0-d916021cecdf@google.com>
%pGg produces nice readable output and decouples the format string from
the size of gfp_t.
Signed-off-by: Brendan Jackman <jackmanb@google.com>
---
net/rds/tcp_recv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/rds/tcp_recv.c b/net/rds/tcp_recv.c
index 49f96ee0c40f6..ffe843ca219c7 100644
--- a/net/rds/tcp_recv.c
+++ b/net/rds/tcp_recv.c
@@ -275,7 +275,7 @@ static int rds_tcp_read_sock(struct rds_conn_path *cp, gfp_t gfp)
desc.count = 1; /* give more than one skb per call */
tcp_read_sock(sock->sk, &desc, rds_tcp_data_recv);
- rdsdebug("tcp_read_sock for tc %p gfp 0x%x returned %d\n", tc, gfp,
+ rdsdebug("tcp_read_sock for tc %p gfp %pGg returned %d\n", tc, &gfp,
desc.error);
if (skb_queue_empty_lockless(&sock->sk->sk_receive_queue) &&
--
2.51.2
next prev parent reply other threads:[~2026-03-26 12:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 12:31 [PATCH v2 0/4] treewide: fixup gfp_t printks Brendan Jackman
2026-03-26 12:31 ` [PATCH v2 1/4] drm/managed: Use special gfp_t format specifier Brendan Jackman
2026-03-26 12:31 ` [PATCH v2 2/4] iwlegacy: 3945-mac: Fixup allocation failure log Brendan Jackman
2026-03-27 11:45 ` Stanislaw Gruszka
2026-03-26 12:31 ` [PATCH v2 3/4] mm/kfence: Use special gfp_t format specifier Brendan Jackman
2026-03-26 12:32 ` Brendan Jackman [this message]
2026-04-02 17:16 ` [PATCH v2 4/4] net/rds: " Allison Henderson
2026-03-27 11:57 ` [PATCH v2 0/4] treewide: fixup gfp_t printks Stanislaw Gruszka
2026-05-12 12:58 ` Brendan Jackman
2026-05-12 21:05 ` Andrew Morton
2026-05-13 9:11 ` Brendan Jackman
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=20260326-gfp64-v2-4-d916021cecdf@google.com \
--to=jackmanb@google.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=allison.henderson@oracle.com \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=horms@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=simona@ffwll.ch \
--cc=stf_xl@wp.pl \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.