From: patchwork-bot+netdevbpf@kernel.org
To: Paul Chaignon <paul@isovalent.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, quentin@isovalent.com
Subject: Re: [PATCH bpf-next 0/3] bpftool: Probes for bounded loops and instruction set extensions
Date: Wed, 05 Jan 2022 12:40:16 +0000 [thread overview]
Message-ID: <164138641615.6231.4937030135518900608.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1641314075.git.paul@isovalent.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 4 Jan 2022 18:57:54 +0100 you wrote:
> This patchset adds feature probes for bounded loops and instruction set
> extensions. The first patch refactors the existing miscellaneous probe
> to avoid code duplication in subsequent patches.
>
> The four miscellaneous probes were tested on kernels 4.9, 4.19, and 5.4.
>
> The feature probe for bounded loops was previously submitted as part of
> patchset https://lore.kernel.org/bpf/20211217211135.GA42088@Mem/T/.
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] bpftool: Refactor misc. feature probe
https://git.kernel.org/bpf/bpf-next/c/b22bf1b9979a
- [bpf-next,2/3] bpftool: Probe for bounded loop support
https://git.kernel.org/bpf/bpf-next/c/c04fb2b0bd92
- [bpf-next,3/3] bpftool: Probe for instruction set extensions
https://git.kernel.org/bpf/bpf-next/c/0fd800b2456c
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-01-05 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 17:57 [PATCH bpf-next 0/3] bpftool: Probes for bounded loops and instruction set extensions Paul Chaignon
2022-01-04 17:59 ` [PATCH bpf-next 1/3] bpftool: Refactor misc. feature probe Paul Chaignon
2022-01-04 17:59 ` [PATCH bpf-next 2/3] bpftool: Probe for bounded loop support Paul Chaignon
2022-01-04 18:00 ` [PATCH bpf-next 3/3] bpftool: Probe for instruction set extensions Paul Chaignon
2022-01-05 12:40 ` 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=164138641615.6231.4937030135518900608.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=paul@isovalent.com \
--cc=quentin@isovalent.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 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.