From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, netdev@vger.kernel.org,
kernel-team@meta.com, eyal.birger@gmail.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Allow building bpf tests with CONFIG_XFRM_INTERFACE=[m|n]
Date: Tue, 06 Dec 2022 21:00:15 +0000 [thread overview]
Message-ID: <167036041551.30610.2678929954116630234.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221206193554.1059757-1-martin.lau@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 6 Dec 2022 11:35:54 -0800 you wrote:
> From: Martin KaFai Lau <martin.lau@kernel.org>
>
> It is useful to use vmlinux.h in the xfrm_info test like other kfunc
> tests do. In particular, it is common for kfunc bpf prog that requires
> to use other core kernel structures in vmlinux.h
>
> Although vmlinux.h is preferred, it needs a ___local flavor of
> struct bpf_xfrm_info in order to build the bpf selftests
> when CONFIG_XFRM_INTERFACE=[m|n].
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Allow building bpf tests with CONFIG_XFRM_INTERFACE=[m|n]
https://git.kernel.org/bpf/bpf-next/c/aa67961f3243
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:[~2022-12-06 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 19:35 [PATCH bpf-next] selftests/bpf: Allow building bpf tests with CONFIG_XFRM_INTERFACE=[m|n] Martin KaFai Lau
2022-12-06 21: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=167036041551.30610.2678929954116630234.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eyal.birger@gmail.com \
--cc=kernel-team@meta.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
/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.