From: patchwork-bot+netdevbpf@kernel.org
To: KP Singh <kpsingh@kernel.org>
Cc: bpf@vger.kernel.org, linux-security-module@vger.kernel.org,
bboscaccy@linux.microsoft.com, paul@paul-moore.com,
kys@microsoft.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org
Subject: Re: [PATCH bpf-next v7 0/5] Signed BPF programs
Date: Tue, 23 Sep 2025 02:30:12 +0000 [thread overview]
Message-ID: <175859461225.1236852.4239631219709272102.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250921160120.9711-1-kpsingh@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 21 Sep 2025 18:01:15 +0200 you wrote:
> # v6 -> v7
>
> * list header mess up in Patch subject
>
> # v5 -> v6
>
> * Rebase again removing the first 7 patches as they are merged already.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/5] bpf: Implement signature verification for BPF programs
https://git.kernel.org/bpf/bpf-next/c/349271568303
- [bpf-next,v7,2/5] libbpf: Update light skeleton for signing
(no matching commit)
- [bpf-next,v7,3/5] libbpf: Embed and verify the metadata hash in the loader
https://git.kernel.org/bpf/bpf-next/c/ea923080c145
- [bpf-next,v7,4/5] bpftool: Add support for signing BPF programs
https://git.kernel.org/bpf/bpf-next/c/40863f4d6ef2
- [bpf-next,v7,5/5] selftests/bpf: Enable signature verification for some lskel tests
https://git.kernel.org/bpf/bpf-next/c/b720903e2b14
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-09-23 2:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 16:01 [PATCH bpf-next v7 0/5] Signed BPF programs KP Singh
2025-09-21 16:01 ` [PATCH bpf-next v7 1/5] bpf: Implement signature verification for " KP Singh
2025-10-07 16:42 ` Chris Mason
2025-09-21 16:01 ` [PATCH bpf-next v7 2/5] libbpf: Update light skeleton for signing KP Singh
2025-09-21 16:01 ` [PATCH bpf-next v7 3/5] libbpf: Embed and verify the metadata hash in the loader KP Singh
2025-09-21 16:01 ` [PATCH bpf-next v7 4/5] bpftool: Add support for signing BPF programs KP Singh
2025-09-22 11:24 ` Quentin Monnet
2025-09-23 2:31 ` Alexei Starovoitov
2025-09-23 8:39 ` Quentin Monnet
2025-09-21 16:01 ` [PATCH bpf-next v7 5/5] selftests/bpf: Enable signature verification for some lskel tests KP Singh
2025-09-23 1:26 ` [PATCH bpf-next v7 0/5] Signed BPF programs Paul Moore
2025-09-23 2:30 ` 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=175859461225.1236852.4239631219709272102.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bboscaccy@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.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