From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/4] Assorted minor socket creation cleanups
Date: Tue, 9 Jun 2026 16:30:01 +1000 [thread overview]
Message-ID: <20260609063005.113744-1-david@gibson.dropbear.id.au> (raw)
As discussed on our recent call, I was looking again at bug 167. I
discovered it's still fairly fiddly to address this, but while
investigating spotted a number of cleanups to make in the vicinity. I
think they make sense even without fixing bug 167 (yet), so here they
are.
David Gibson (4):
flow: Correct misleading signature of flowside_sock_l4()
Makefile: Remove unused DUAL_STACK_SOCKETS define
fwd, pif: Remove duplicated logic between tcp_listen() and
udp_listen()
pif, util: Move listen(2) call from sock_l4_() to pif_listen()
Makefile | 5 -----
flow.c | 11 +++++------
fwd.c | 8 +-------
pif.c | 45 ++++++++++++++++++++++++++++++++++++---------
pif.h | 2 +-
tcp.c | 38 --------------------------------------
tcp.h | 2 --
udp.c | 38 --------------------------------------
udp.h | 2 --
util.c | 7 -------
10 files changed, 43 insertions(+), 115 deletions(-)
--
2.54.0
next reply other threads:[~2026-06-09 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 6:30 David Gibson [this message]
2026-06-09 6:30 ` [PATCH 1/4] flow: Correct misleading signature of flowside_sock_l4() David Gibson
2026-06-09 6:30 ` [PATCH 2/4] Makefile: Remove unused DUAL_STACK_SOCKETS define David Gibson
2026-06-09 6:30 ` [PATCH 3/4] fwd, pif: Remove duplicated logic between tcp_listen() and udp_listen() David Gibson
2026-06-09 6:30 ` [PATCH 4/4] pif, util: Move listen(2) call from sock_l4_() to pif_listen() 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=20260609063005.113744-1-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).