From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>,
Laurent Vivier <lvivier@redhat.com>
Subject: [PATCH v3 2/5] tcp: Fix coding style for comment to enum tcp_iov_parts
Date: Sat, 6 Dec 2025 02:26:54 +0100 [thread overview]
Message-ID: <20251206012657.553742-3-sbrivio@redhat.com> (raw)
In-Reply-To: <20251206012657.553742-1-sbrivio@redhat.com>
...as I'm going to add a new value to it.
Fixes: 95601237ef82 ("tcp: Replace TCP buffer structure by an iovec array")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
---
tcp_internal.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tcp_internal.h b/tcp_internal.h
index f55025c..19e8922 100644
--- a/tcp_internal.h
+++ b/tcp_internal.h
@@ -57,7 +57,7 @@
#define CONN_V4(conn) (!!inany_v4(&TAPFLOW(conn)->oaddr))
#define CONN_V6(conn) (!CONN_V4(conn))
-/*
+/**
* enum tcp_iov_parts - I/O vector parts for one TCP frame
* @TCP_IOV_TAP tap backend specific header
* @TCP_IOV_ETH Ethernet header
--
2.43.0
next prev parent reply other threads:[~2025-12-06 1:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 1:26 [PATCH v3 0/5] Pad all inbound frames to 802.3 minimum size if needed Stefano Brivio
2025-12-06 1:26 ` [PATCH v3 1/5] tap: Pad non-batched frames to 802.3 minimum (60 bytes) " Stefano Brivio
2025-12-06 1:26 ` Stefano Brivio [this message]
2025-12-06 1:26 ` [PATCH v3 3/5] udp: Fix coding style for comment to enum udp_iov_idx Stefano Brivio
2025-12-06 1:26 ` [PATCH v3 4/5] tcp, udp: Pad batched frames to 60 bytes (802.3 minimum) in non-vhost-user modes Stefano Brivio
2025-12-08 2:04 ` David Gibson
2025-12-06 1:26 ` [PATCH v3 5/5] tcp, udp: Pad batched frames for vhost-user modes to 60 bytes (802.3 minimum) Stefano Brivio
2025-12-08 2:16 ` 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=20251206012657.553742-3-sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
/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).