From: patchwork-bot+netdevbpf@kernel.org
To: Christian Brauner <brauner@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, bpf@vger.kernel.org,
kpsingh@kernel.org, andrii@kernel.org, martin.lau@linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2 0/2] bpf: classify block device hooks and add selftests
Date: Fri, 27 Mar 2026 16:10:14 +0000 [thread overview]
Message-ID: <177462781479.3551071.3975124198098746090.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260326-work-bpf-bdev-v2-0-5e3c58963987@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 26 Mar 2026 17:09:13 +0100 you wrote:
> A bunch of new hooks for managing block devices were added a while ago
> but they weren't appropriately classified. Classify them and add a test
> program so we catch regressions.
>
> Note that for whatever reason building the bpf selftests locally seems
> to fail for all kinds of arcane reasons for me. That might just be my
> fault. I added a pr against the ci to have the selftests run but to test
> this meaningfully it needs veritysetup and dmverity support. I'm not
> sure if that's available already.
>
> [...]
Here is the summary with links:
- [RESEND,v2,1/2] bpf: classify block device hooks appropriately
https://git.kernel.org/bpf/bpf-next/c/46df585fcff7
- [RESEND,v2,2/2] selftests/bpf: add block device management selftests
https://git.kernel.org/bpf/bpf-next/c/96f4c251a087
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-03-27 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 16:09 [PATCH RESEND v2 0/2] bpf: classify block device hooks and add selftests Christian Brauner
2026-03-26 16:09 ` [PATCH RESEND v2 1/2] bpf: classify block device hooks appropriately Christian Brauner
2026-03-26 16:09 ` [PATCH RESEND v2 2/2] selftests/bpf: add block device management selftests Christian Brauner
2026-03-27 16: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=177462781479.3551071.3975124198098746090.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=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox