From: patchwork-bot+netdevbpf@kernel.org
To: Anton Protopopov <a.s.protopopov@gmail.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org
Subject: Re: [PATCH v2 bpf-next 0/2] likely/unlikely for bpf_helpers and a small comment fix
Date: Fri, 04 Apr 2025 16:00:36 +0000 [thread overview]
Message-ID: <174378243676.3310001.16730699009629085567.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250331203618.1973691-1-a.s.protopopov@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 31 Mar 2025 20:36:16 +0000 you wrote:
> These two commits fix a comment describing bpf_attr in <linux/bpf.h>
> and add likely/unlikely macros to <bph/bpf_helpers.h> to be consumed
> by selftests and, later, by the static_branch_likely/unlikely macros.
>
> v1 -> v2:
> * squash libbpf and selftests fixes into one patch (Andrii)
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: fix a comment describing bpf_attr
https://git.kernel.org/bpf/bpf-next/c/62aa5790cec8
- [bpf-next,2/2] libbpf: add likely/unlikely macros and use them in selftests
https://git.kernel.org/bpf/bpf-next/c/dafae1ae2ad3
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-04-04 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 20:36 [PATCH v2 bpf-next 0/2] likely/unlikely for bpf_helpers and a small comment fix Anton Protopopov
2025-03-31 20:36 ` [PATCH bpf-next 1/2] bpf: fix a comment describing bpf_attr Anton Protopopov
2025-03-31 20:36 ` [PATCH bpf-next 2/2] libbpf: add likely/unlikely macros and use them in selftests Anton Protopopov
2025-04-04 16:00 ` 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=174378243676.3310001.16730699009629085567.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.s.protopopov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
/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