From: Martin KaFai Lau <martin.lau@linux.dev>
To: Hoyeon Lee <hoyeon.lee@suse.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
daniel@iogearbox.net, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, Amery Hung <ameryhung@gmail.com>
Subject: Re: [PATCH bpf-next v2 0/2] selftests/bpf: networking test cleanups
Date: Fri, 21 Nov 2025 10:53:25 -0800 [thread overview]
Message-ID: <5aee549c-5ae2-45a7-b658-7918d2a918cb@linux.dev> (raw)
In-Reply-To: <20251121081332.2309838-1-hoyeon.lee@suse.com>
On 11/21/25 12:13 AM, Hoyeon Lee wrote:
> This series finishes the sockaddr_storage migration in the networking
> selftests by removing the remaining open-coded IPv4/IPv6 wrappers
> (addr_port/tuple in cls_redirect, sa46 in select_reuseport). The tests
> now use sockaddr_storage directly. No other custom socket-address
> wrappers remain after this series, so the churn stops here and behavior
> is unchanged.
I added Amery's Reviewed-by. Please keep the tag in the future when the
newer revision doesn't have major changes.
Applied. Thanks.
next prev parent reply other threads:[~2025-11-21 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 8:13 [PATCH bpf-next v2 0/2] selftests/bpf: networking test cleanups Hoyeon Lee
2025-11-21 8:13 ` [PATCH bpf-next v2 1/2] selftests/bpf: use sockaddr_storage directly in cls_redirect test Hoyeon Lee
2025-11-21 8:13 ` [PATCH bpf-next v2 2/2] selftests/bpf: use sockaddr_storage instead of sa46 in select_reuseport test Hoyeon Lee
2025-11-21 18:53 ` Martin KaFai Lau [this message]
2025-11-21 19:00 ` [PATCH bpf-next v2 0/2] selftests/bpf: networking test cleanups patchwork-bot+netdevbpf
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=5aee549c-5ae2-45a7-b658-7918d2a918cb@linux.dev \
--to=martin.lau@linux.dev \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hoyeon.lee@suse.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.