From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, acme@redhat.com,
ast@kernel.org, daniel@iogearbox.net, jolsa@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, mcgrof@kernel.org, masahiroy@kernel.org,
nathan@kernel.org, mykolal@fb.com, thinker.li@gmail.com,
bentiss@kernel.org, tanggeliang@kylinos.cn, bpf@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next 0/6] bpf: resilient split BTF followups
Date: Fri, 21 Jun 2024 22:10:31 +0000 [thread overview]
Message-ID: <171900783146.8103.14964230406713262563.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240620091733.1967885-1-alan.maguire@oracle.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 20 Jun 2024 10:17:27 +0100 you wrote:
> Follow-up to resilient split BTF series [1],
>
> - cleaning up libbpf relocation code (patch 1);
> - adding 'struct module' support for base BTF data (patch 2);
> - splitting out field iteration code into separate file (patch 3);
> - sharing libbpf relocation code with the kernel (patch 4);
> - adding a kbuild --btf_features flag to generate distilled base
> BTF in the module-specific case where KBUILD_EXTMOD is true
> (patch 5); and
> - adding test coverage for module-based kfunc dtor (patch 6)
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/6] libbpf: BTF relocation followup fixing naming, loop logic
https://git.kernel.org/bpf/bpf-next/c/d1cf840854bb
- [v2,bpf-next,2/6] module, bpf: store BTF base pointer in struct module
https://git.kernel.org/bpf/bpf-next/c/d4e48e3dd450
- [v2,bpf-next,3/6] libbpf: split field iter code into its own file kernel
https://git.kernel.org/bpf/bpf-next/c/e7ac331b3055
- [v2,bpf-next,4/6] libbpf,bpf: share BTF relocate-related code with kernel
https://git.kernel.org/bpf/bpf-next/c/8646db238997
- [v2,bpf-next,5/6] kbuild,bpf: add module-specific pahole flags for distilled base BTF
https://git.kernel.org/bpf/bpf-next/c/46fb0b62ea29
- [v2,bpf-next,6/6] selftests/bpf: add kfunc_call test for simple dtor in bpf_testmod
https://git.kernel.org/bpf/bpf-next/c/47a8cf0c5b3f
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:[~2024-06-21 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 9:17 [PATCH v2 bpf-next 0/6] bpf: resilient split BTF followups Alan Maguire
2024-06-20 9:17 ` [PATCH v2 bpf-next 1/6] libbpf: BTF relocation followup fixing naming, loop logic Alan Maguire
2024-06-20 9:17 ` [PATCH v2 bpf-next 2/6] module, bpf: store BTF base pointer in struct module Alan Maguire
2024-06-20 9:17 ` [PATCH v2 bpf-next 3/6] libbpf: split field iter code into its own file kernel Alan Maguire
2024-06-20 9:17 ` [PATCH v2 bpf-next 4/6] libbpf,bpf: share BTF relocate-related code with kernel Alan Maguire
2024-06-20 9:17 ` [PATCH v2 bpf-next 5/6] kbuild,bpf: add module-specific pahole flags for distilled base BTF Alan Maguire
2024-06-20 9:17 ` [PATCH v2 bpf-next 6/6] selftests/bpf: add kfunc_call test for simple dtor in bpf_testmod Alan Maguire
2024-06-20 11:41 ` Eduard Zingerman
2024-06-21 22:00 ` Andrii Nakryiko
2024-06-21 22: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=171900783146.8103.14964230406713262563.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@redhat.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bentiss@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=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=mykolal@fb.com \
--cc=nathan@kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tanggeliang@kylinos.cn \
--cc=thinker.li@gmail.com \
--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.