From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, alexis.lothore@bootlin.com,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf] selftests/bpf: Support when CONFIG_VXLAN=m
Date: Fri, 16 Jan 2026 23:00:09 +0000 [thread overview]
Message-ID: <176860440952.828763.9055728043184297613.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260115163457.146267-1-alan.maguire@oracle.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 15 Jan 2026 16:34:57 +0000 you wrote:
> If CONFIG_VXLAN is 'm', struct vxlanhdr will not be in vmlinux.h.
> Add a ___local variant to support cases where vxlan is a module.
>
> Fixes: 8517b1abe5ea ("selftests/bpf: Integrate test_tc_tunnel.sh tests into test_progs")
> Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
> ---
> .../selftests/bpf/progs/test_tc_tunnel.c | 21 ++++++++++++-------
> 1 file changed, 13 insertions(+), 8 deletions(-)
Here is the summary with links:
- [bpf] selftests/bpf: Support when CONFIG_VXLAN=m
https://git.kernel.org/bpf/bpf-next/c/47d440d0a5bb
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:[~2026-01-16 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 16:34 [PATCH bpf] selftests/bpf: Support when CONFIG_VXLAN=m Alan Maguire
2026-01-16 8:30 ` Alexis Lothoré
2026-01-16 9:32 ` Alan Maguire
2026-01-19 13:00 ` Alexis Lothoré
2026-01-19 17:13 ` Alexei Starovoitov
2026-01-16 23:00 ` 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=176860440952.828763.9055728043184297613.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=alexis.lothore@bootlin.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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--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.