From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Daniel_M=C3=BCller_=3Cdeso=40posteo=2Enet=3E?=@ci.codeaurora.org
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, mykolal@fb.com,
kafai@fb.com
Subject: Re: [PATCH bpf-next v4 0/3] Maintain selftest configuration in-tree
Date: Wed, 27 Jul 2022 15:10:13 +0000 [thread overview]
Message-ID: <165893461358.29339.11641967418379627671.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220727001156.3553701-1-deso@posteo.net>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 27 Jul 2022 00:11:53 +0000 you wrote:
> BPF selftests mandate certain kernel configuration options to be present in
> order to pass. Currently the "reference" config files containing these options
> are hosted in a separate repository [0]. From there they are picked up by the
> BPF continuous integration system as well as the in-tree vmtest.sh helper
> script, which allows for running tests in a VM-based setup locally.
>
> But it gets worse, as "BPF CI" is really two CI systems: one for libbpf
> (mentioned above) and one for the bpf-next kernel repository (or more precisely:
> family of repositories, as bpf-rc is using the system). As such, we have an
> additional -- and slightly divergent -- copy of these configurations.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/3] selftests/bpf: Sort configuration
https://git.kernel.org/bpf/bpf-next/c/aee993bbd05c
- [bpf-next,v4,2/3] selftests/bpf: Copy over libbpf configs
https://git.kernel.org/bpf/bpf-next/c/cbd620fc18ca
- [bpf-next,v4,3/3] selftests/bpf: Adjust vmtest.sh to use local kernel configuration
https://git.kernel.org/bpf/bpf-next/c/40b09653b197
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-07-27 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 0:11 [PATCH bpf-next v4 0/3] Maintain selftest configuration in-tree Daniel Müller
2022-07-27 0:11 ` [PATCH bpf-next v4 1/3] selftests/bpf: Sort configuration Daniel Müller
2022-07-27 0:11 ` [PATCH bpf-next v4 2/3] selftests/bpf: Copy over libbpf configs Daniel Müller
2022-07-27 0:11 ` [PATCH bpf-next v4 3/3] selftests/bpf: Adjust vmtest.sh to use local kernel configuration Daniel Müller
2022-07-27 15: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=165893461358.29339.11641967418379627671.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Daniel_M=C3=BCller_=3Cdeso=40posteo=2Enet=3E?=@ci.codeaurora.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=mykolal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox