From: patchwork-bot+netdevbpf@kernel.org
To: Hoyeon Lee <hoyeon.lee@suse.com>
Cc: bpf@vger.kernel.org, nathan@kernel.org,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
justinstitt@google.com, llvm@lists.linux.dev
Subject: Re: [bpf-next v1 0/5] selftests/bpf: networking test cleanups and build fix
Date: Tue, 18 Nov 2025 23:10:07 +0000 [thread overview]
Message-ID: <176350740725.137683.16243703644793290914.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251115225550.1086693-1-hoyeon.lee@suse.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Sun, 16 Nov 2025 07:55:35 +0900 you wrote:
> This series refactors several networking-related BPF selftests and fixes
> a toolchain propagation issue in runqslower.
>
> The first four patches simplify networking selftests by removing custom
> IPv4/IPv6 address wrappers, migrating to sockaddr_storage, dropping
> duplicated TCP helpers, and replacing open-coded congestion-control
> string checks with bpf_strncmp(). These changes reduce duplication and
> improve consistency without altering test behavior.
>
> [...]
Here is the summary with links:
- [bpf-next,v1,1/5] selftests/bpf: use sockaddr_storage instead of addr_port in cls_redirect test
(no matching commit)
- [bpf-next,v1,2/5] selftests/bpf: use sockaddr_storage instead of sa46 in select_reuseport test
(no matching commit)
- [bpf-next,v1,3/5] selftests/bpf: move common TCP helpers into bpf_tracing_net.h
https://git.kernel.org/bpf/bpf-next/c/f700b37314d9
- [bpf-next,v1,4/5] selftests/bpf: replace TCP CC string comparisons with bpf_strncmp
https://git.kernel.org/bpf/bpf-next/c/ec12ab2cda66
- [bpf-next,v1,5/5] selftests/bpf: propagate LLVM toolchain to runqslower build
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-18 23:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 22:55 [bpf-next v1 0/5] selftests/bpf: networking test cleanups and build fix Hoyeon Lee
2025-11-15 22:55 ` [bpf-next v1 1/5] selftests/bpf: use sockaddr_storage instead of addr_port in cls_redirect test Hoyeon Lee
2025-11-18 23:12 ` Martin KaFai Lau
2025-11-19 3:09 ` Hoyeon Lee
2025-11-19 16:57 ` Martin KaFai Lau
2025-11-15 22:55 ` [bpf-next v1 2/5] selftests/bpf: use sockaddr_storage instead of sa46 in select_reuseport test Hoyeon Lee
2025-11-15 22:55 ` [bpf-next v1 3/5] selftests/bpf: move common TCP helpers into bpf_tracing_net.h Hoyeon Lee
2025-11-15 22:55 ` [bpf-next v1 4/5] selftests/bpf: replace TCP CC string comparisons with bpf_strncmp Hoyeon Lee
2025-11-15 22:55 ` [bpf-next v1 5/5] selftests/bpf: propagate LLVM toolchain to runqslower build Hoyeon Lee
2025-11-17 6:04 ` Yonghong Song
2025-11-17 6:37 ` Hoyeon Lee
2025-11-17 23:16 ` [bpf-next v1 0/5] selftests/bpf: networking test cleanups and build fix Amery Hung
2025-11-18 23:10 ` patchwork-bot+netdevbpf [this message]
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=176350740725.137683.16243703644793290914.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=hoyeon.lee@suse.com \
--cc=justinstitt@google.com \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.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.
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.