public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
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, void@manifault.com
Subject: Re: [PATCH bpf-next 0/3] Support passing BPF iterator to kfuncs
Date: Wed, 21 Aug 2024 17:50:30 +0000	[thread overview]
Message-ID: <172426263000.1792219.7842087803669646661.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240808232230.2848712-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu,  8 Aug 2024 16:22:27 -0700 you wrote:
> Add support for passing BPF iterator state to any kfunc. Such kfunc has to
> declare such argument with valid `struct bpf_iter_<type> *` type and should
> use "__iter" suffix in argument name, following the established suffix-based
> convention. We add a simple test/demo iterator getter in bpf_testmod.
> 
> Andrii Nakryiko (3):
>   bpf: extract iterator argument type and name validation logic
>   bpf: allow passing struct bpf_iter_<type> as kfunc arguments
>   selftests/bpf: test passing iterator to a kfunc
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/3] bpf: extract iterator argument type and name validation logic
    https://git.kernel.org/bpf/bpf-next/c/496ddd19a0fa
  - [bpf-next,2/3] bpf: allow passing struct bpf_iter_<type> as kfunc arguments
    https://git.kernel.org/bpf/bpf-next/c/baebe9aaba1e
  - [bpf-next,3/3] selftests/bpf: test passing iterator to a kfunc
    https://git.kernel.org/bpf/bpf-next/c/b0cd726f9a82

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-08-21 17:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 23:22 [PATCH bpf-next 0/3] Support passing BPF iterator to kfuncs Andrii Nakryiko
2024-08-08 23:22 ` [PATCH bpf-next 1/3] bpf: extract iterator argument type and name validation logic Andrii Nakryiko
2024-08-09 18:38   ` Eduard Zingerman
2024-08-08 23:22 ` [PATCH bpf-next 2/3] bpf: allow passing struct bpf_iter_<type> as kfunc arguments Andrii Nakryiko
2024-08-09 19:14   ` Eduard Zingerman
2024-08-09 19:28     ` Andrii Nakryiko
2024-08-09 19:40       ` Eduard Zingerman
2024-08-09 20:36         ` Andrii Nakryiko
2024-08-08 23:22 ` [PATCH bpf-next 3/3] selftests/bpf: test passing iterator to a kfunc Andrii Nakryiko
2024-08-21 17:50 ` 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=172426263000.1792219.7842087803669646661.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=martin.lau@kernel.org \
    --cc=tj@kernel.org \
    --cc=void@manifault.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