From: patchwork-bot+netdevbpf@kernel.org
To: D. Wythe <alibuda@linux.alibaba.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, pabeni@redhat.com, song@kernel.org,
sdf@google.com, haoluo@google.com, yhs@fb.com,
edumazet@google.com, john.fastabend@gmail.com,
kpsingh@kernel.org, jolsa@kernel.org, mjambigi@linux.ibm.com,
wenjia@linux.ibm.com, wintera@linux.ibm.com,
dust.li@linux.alibaba.com, tonylu@linux.alibaba.com,
guwen@linux.alibaba.com, bpf@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
sidraya@linux.ibm.com, jaka@linux.ibm.com
Subject: Re: [PATCH bpf-next v5 0/3] net/smc: Introduce smc_hs_ctrl
Date: Mon, 10 Nov 2025 20:10:13 +0000 [thread overview]
Message-ID: <176280541325.2759707.7993878047530807107.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251107035632.115950-1-alibuda@linux.alibaba.com>
Hello:
This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Fri, 7 Nov 2025 11:56:29 +0800 you wrote:
> This patch aims to introduce BPF injection capabilities for SMC and
> includes a self-test to ensure code stability.
>
> Since the SMC protocol isn't ideal for every situation, especially
> short-lived ones, most applications can't guarantee the absence of
> such scenarios. Consequently, applications may need specific strategies
> to decide whether to use SMC. For example, an application might limit SMC
> usage to certain IP addresses or ports.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/3] bpf: export necessary symbols for modules with struct_ops
https://git.kernel.org/bpf/bpf-next/c/07c428ece322
- [bpf-next,v5,2/3] net/smc: bpf: Introduce generic hook for handshake flow
https://git.kernel.org/bpf/bpf-next/c/15f295f55656
- [bpf-next,v5,3/3] bpf/selftests: add selftest for bpf_smc_hs_ctrl
https://git.kernel.org/bpf/bpf-next/c/beb3c67297d9
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-10 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 3:56 [PATCH bpf-next v5 0/3] net/smc: Introduce smc_hs_ctrl D. Wythe
2025-11-07 3:56 ` [PATCH bpf-next v5 1/3] bpf: export necessary symbols for modules with struct_ops D. Wythe
2025-11-07 3:56 ` [PATCH bpf-next v5 2/3] net/smc: bpf: Introduce generic hook for handshake flow D. Wythe
2025-12-05 4:16 ` Guenter Roeck
2025-12-16 6:43 ` D. Wythe
2025-11-07 3:56 ` [PATCH bpf-next v5 3/3] bpf/selftests: add selftest for bpf_smc_hs_ctrl D. Wythe
2025-11-07 4:16 ` bot+bpf-ci
2025-11-10 23:28 ` Martin KaFai Lau
2025-11-10 20: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=176280541325.2759707.7993878047530807107.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=haoluo@google.com \
--cc=jaka@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=sidraya@linux.ibm.com \
--cc=song@kernel.org \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.com \
--cc=yhs@fb.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.