All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, eddyz87@gmail.com, yatsenko@meta.com,
	tj@kernel.org, alan.maguire@oracle.com, bentiss@kernel.org,
	jikos@kernel.org, ameryhung@gmail.com, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	sched-ext@lists.linux.dev
Subject: Re: [PATCH bpf-next v3 00/13] bpf: Kernel functions with KF_IMPLICIT_ARGS
Date: Wed, 21 Jan 2026 00:30:20 +0000	[thread overview]
Message-ID: <176895542010.663774.16633470038935987737.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260120222638.3976562-1-ihor.solodrai@linux.dev>

Hello:

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

On Tue, 20 Jan 2026 14:26:25 -0800 you wrote:
> This series implements a generic "implicit arguments" feature for BPF
> kernel functions. For context see prior work [1][2].
> 
> A mechanism is created for kfuncs to have arguments that are not
> visible to the BPF programs, and are provided to the kernel function
> implementation by the verifier.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,01/13] bpf: Refactor btf_kfunc_id_set_contains
    https://git.kernel.org/bpf/bpf-next/c/ea073d1818e2
  - [bpf-next,v3,02/13] bpf: Introduce struct bpf_kfunc_meta
    https://git.kernel.org/bpf/bpf-next/c/08ca87d63243
  - [bpf-next,v3,03/13] bpf: Verifier support for KF_IMPLICIT_ARGS
    https://git.kernel.org/bpf/bpf-next/c/64e1360524b9
  - [bpf-next,v3,04/13] resolve_btfids: Introduce finalize_btf() step
    https://git.kernel.org/bpf/bpf-next/c/2583e81fd885
  - [bpf-next,v3,05/13] resolve_btfids: Support for KF_IMPLICIT_ARGS
    https://git.kernel.org/bpf/bpf-next/c/9d199965990c
  - [bpf-next,v3,06/13] selftests/bpf: Add tests for KF_IMPLICIT_ARGS
    https://git.kernel.org/bpf/bpf-next/c/e939f3d16d77
  - [bpf-next,v3,07/13] bpf: Migrate bpf_wq_set_callback_impl() to KF_IMPLICIT_ARGS
    https://git.kernel.org/bpf/bpf-next/c/b97931a25a4b
  - [bpf-next,v3,08/13] HID: Use bpf_wq_set_callback kernel function
    https://git.kernel.org/bpf/bpf-next/c/8157cc739ad3
  - [bpf-next,v3,09/13] bpf: Migrate bpf_task_work_schedule_* kfuncs to KF_IMPLICIT_ARGS
    (no matching commit)
  - [bpf-next,v3,10/13] bpf: Migrate bpf_stream_vprintk() to KF_IMPLICIT_ARGS
    https://git.kernel.org/bpf/bpf-next/c/d806f3101276
  - [bpf-next,v3,11/13] selftests/bpf: Migrate struct_ops_assoc test to KF_IMPLICIT_ARGS
    https://git.kernel.org/bpf/bpf-next/c/bd06b977e02d
  - [bpf-next,v3,12/13] bpf: Remove __prog kfunc arg annotation
    https://git.kernel.org/bpf/bpf-next/c/aed57a363871
  - [bpf-next,v3,13/13] bpf,docs: Document KF_IMPLICIT_ARGS flag
    https://git.kernel.org/bpf/bpf-next/c/74bc4f612720

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



      parent reply	other threads:[~2026-01-21  0:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 22:26 [PATCH bpf-next v3 00/13] bpf: Kernel functions with KF_IMPLICIT_ARGS Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 01/13] bpf: Refactor btf_kfunc_id_set_contains Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 02/13] bpf: Introduce struct bpf_kfunc_meta Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 03/13] bpf: Verifier support for KF_IMPLICIT_ARGS Ihor Solodrai
2026-01-21  0:30   ` Alexei Starovoitov
2026-01-21  0:35     ` Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 04/13] resolve_btfids: Introduce finalize_btf() step Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 05/13] resolve_btfids: Support for KF_IMPLICIT_ARGS Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 06/13] selftests/bpf: Add tests " Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 07/13] bpf: Migrate bpf_wq_set_callback_impl() to KF_IMPLICIT_ARGS Ihor Solodrai
2026-01-20 22:55   ` bot+bpf-ci
2026-01-20 23:04     ` Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 08/13] HID: Use bpf_wq_set_callback kernel function Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 09/13] bpf: Migrate bpf_task_work_schedule_* kfuncs to KF_IMPLICIT_ARGS Ihor Solodrai
2026-01-21  0:28   ` Alexei Starovoitov
2026-01-20 22:26 ` [PATCH bpf-next v3 10/13] bpf: Migrate bpf_stream_vprintk() " Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 11/13] selftests/bpf: Migrate struct_ops_assoc test " Ihor Solodrai
2026-01-20 22:26 ` [PATCH bpf-next v3 12/13] bpf: Remove __prog kfunc arg annotation Ihor Solodrai
2026-01-20 22:30 ` [PATCH bpf-next v3 13/13] bpf,docs: Document KF_IMPLICIT_ARGS flag Ihor Solodrai
2026-01-21  0:30 ` 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=176895542010.663774.16633470038935987737.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bentiss@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sched-ext@lists.linux.dev \
    --cc=tj@kernel.org \
    --cc=yatsenko@meta.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.