From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, tj@kernel.org, kernel-team@meta.com,
memxor@gmail.com
Subject: Re: [PATCH v2 bpf-next] bpf, docs: document open-coded BPF iterators
Date: Sat, 10 May 2025 06:00:30 +0000 [thread overview]
Message-ID: <174685683027.3903960.5546015291851693456.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250509180350.2604946-1-andrii@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 9 May 2025 11:03:50 -0700 you wrote:
> Extract BPF open-coded iterators documentation spread out across a few
> original commit messages ([0], [1]) into a dedicated doc section under
> Documentation/bpf/bpf_iterators.rst. Also make explicit expectation that
> BPF iterator program type should be accompanied by a corresponding
> open-coded BPF iterator implementation, going forward.
>
> [0] https://lore.kernel.org/all/20230308184121.1165081-3-andrii@kernel.org/
> [1] https://lore.kernel.org/all/20230308184121.1165081-4-andrii@kernel.org/
>
> [...]
Here is the summary with links:
- [v2,bpf-next] bpf, docs: document open-coded BPF iterators
https://git.kernel.org/bpf/bpf-next/c/7220eabff8cb
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-05-10 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 18:03 [PATCH v2 bpf-next] bpf, docs: document open-coded BPF iterators Andrii Nakryiko
2025-05-10 6: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=174685683027.3903960.5546015291851693456.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=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=tj@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 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.