From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 1/5] tcp: Remove extra space from TCP_INFO debug messages (trivial)
Date: Fri, 12 Dec 2025 18:10:34 +1100 [thread overview]
Message-ID: <20251212071038.3943933-2-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20251212071038.3943933-1-david@gibson.dropbear.id.au>
Debug messages about which tcp_info fields are supported contained an
extra space, always ending with " supported".
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
tcp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tcp.c b/tcp.c
index 1711bcc7..81bc1145 100644
--- a/tcp.c
+++ b/tcp.c
@@ -2950,7 +2950,7 @@ int tcp_init(struct ctx *c)
tcp_info_size = tcp_probe_tcp_info();
#define dbg_tcpi(f_) debug("TCP_INFO tcpi_%s field%s supported", \
- STRINGIFY(f_), tcp_info_cap(f_) ? " " : " not ")
+ STRINGIFY(f_), tcp_info_cap(f_) ? "" : " not")
dbg_tcpi(snd_wnd);
dbg_tcpi(bytes_acked);
dbg_tcpi(min_rtt);
--
2.52.0
next prev parent reply other threads:[~2025-12-12 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 7:10 [PATCH 0/5] RFC: Forwarding table data structure David Gibson
2025-12-12 7:10 ` David Gibson [this message]
2025-12-12 7:10 ` [PATCH 2/5] conf, fwd: Move initialisation of auto port scanning out of conf() David Gibson
2025-12-12 7:10 ` [PATCH 3/5] conf, fwd: Keep a table of our port forwarding configuration David Gibson
2025-12-12 7:10 ` [PATCH 4/5] conf: Accurately record ifname and address for outbound forwards David Gibson
2025-12-12 7:10 ` [PATCH 5/5] conf, fwd: Record "auto" port forwards in forwarding table David Gibson
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=20251212071038.3943933-2-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).