From: patchwork-bot+netdevbpf@kernel.org
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: thinker.li@gmail.com, martin.lau@linux.dev,
alibuda@linux.alibaba.com, dust.li@linux.alibaba.com,
ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
sidraya@linux.ibm.com, wenjia@linux.ibm.com,
mjambigi@linux.ibm.com, tonylu@linux.alibaba.com,
guwen@linux.alibaba.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, bpf@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] bpf, net: Fix smc for CONFIG_BPF_JIT=n
Date: Thu, 04 Dec 2025 19:20:06 +0000 [thread overview]
Message-ID: <176487600628.940161.471761997237181377.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1764843476.git.geert@linux-m68k.org>
Hello:
This series was applied to bpf/bpf.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Thu, 4 Dec 2025 11:29:14 +0100 you wrote:
> Hi all,
>
> If CONFIG_BPF_SYSCALL=y, but CONFIG_BPF_JIT=n (e.g. m68k/allmodconfig),
> net/smc/smc_hs_bpf.c fails to build.
>
> This patch series fix the issue in two ways, by:
> 1. fixing the dummy variant of register_bpf_struct_ops(),
> 2. making SMC_HS_CTRL_BPF depend on BPF_JIT.
>
> [...]
Here is the summary with links:
- [1/2] bpf: Fix register_bpf_struct_ops() dummy
(no matching commit)
- [2/2] net: smc: SMC_HS_CTRL_BPF should depend on BPF_JIT
https://git.kernel.org/bpf/bpf/c/861111b69896
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-12-04 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 10:29 [PATCH 0/2] bpf, net: Fix smc for CONFIG_BPF_JIT=n Geert Uytterhoeven
2025-12-04 19:20 ` 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=176487600628.940161.471761997237181377.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--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=geert@linux-m68k.org \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=thinker.li@gmail.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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.