Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Leon Hwang <leon.hwang@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	john.fastabend@gmail.com, andrii@kernel.org,
	martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
	yonghong.song@linux.dev, kpsingh@kernel.org, sdf@fomichev.me,
	haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
	brauner@kernel.org, sforshee@kernel.org, yuichtsu@amazon.com,
	aalbersh@redhat.com, willemb@google.com,
	kerneljasonxing@gmail.com, chen.dylane@linux.dev,
	yatsenko@meta.com, memxor@gmail.com, a.s.protopopov@gmail.com,
	ameryhung@gmail.com, rongtao@cestc.cn,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	linux-kselftest@vger.kernel.org, kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next v14 0/8] bpf: Extend BPF syscall with common attributes support
Date: Tue, 12 May 2026 19:50:16 +0000	[thread overview]
Message-ID: <177861541680.3056308.7326619347008693525.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260512153157.28382-1-leon.hwang@linux.dev>

Hello:

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

On Tue, 12 May 2026 23:31:49 +0800 you wrote:
> This patch series builds upon the discussion in
> "[PATCH bpf-next v4 0/4] bpf: Improve error reporting for freplace attachment failure" [1].
> 
> This patch series introduces support for *common attributes* in the BPF
> syscall, providing a unified mechanism for passing shared metadata across
> all BPF commands, initially used by BPF_PROG_LOAD, BPF_BTF_LOAD, and
> BPF_MAP_CREATE.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v14,1/8] bpf: Extend BPF syscall with common attributes support
    https://git.kernel.org/bpf/bpf-next/c/f28771c0691b
  - [bpf-next,v14,2/8] libbpf: Add support for extended BPF syscall
    https://git.kernel.org/bpf/bpf-next/c/b1bff4080942
  - [bpf-next,v14,3/8] bpf: Refactor reporting log_true_size for prog_load
    https://git.kernel.org/bpf/bpf-next/c/503c039ffeca
  - [bpf-next,v14,4/8] bpf: Add syscall common attributes support for prog_load
    https://git.kernel.org/bpf/bpf-next/c/ac89d33fdd81
  - [bpf-next,v14,5/8] bpf: Add syscall common attributes support for btf_load
    https://git.kernel.org/bpf/bpf-next/c/ceeb7eda94a3
  - [bpf-next,v14,6/8] bpf: Add syscall common attributes support for map_create
    https://git.kernel.org/bpf/bpf-next/c/49f9b2b2a18c
  - [bpf-next,v14,7/8] libbpf: Add syscall common attributes support for map_create
    https://git.kernel.org/bpf/bpf-next/c/702259006f93
  - [bpf-next,v14,8/8] selftests/bpf: Add tests to verify map create failure log
    https://git.kernel.org/bpf/bpf-next/c/f675483cac1d

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-05-12 19:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 15:31 [PATCH bpf-next v14 0/8] bpf: Extend BPF syscall with common attributes support Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 1/8] " Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 2/8] libbpf: Add support for extended BPF syscall Leon Hwang
2026-05-12 16:23   ` bot+bpf-ci
2026-05-13  2:10     ` Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 3/8] bpf: Refactor reporting log_true_size for prog_load Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 4/8] bpf: Add syscall common attributes support " Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 5/8] bpf: Add syscall common attributes support for btf_load Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 6/8] bpf: Add syscall common attributes support for map_create Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 7/8] libbpf: " Leon Hwang
2026-05-12 15:31 ` [PATCH bpf-next v14 8/8] selftests/bpf: Add tests to verify map create failure log Leon Hwang
2026-05-12 19: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=177861541680.3056308.7326619347008693525.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=a.s.protopopov@gmail.com \
    --cc=aalbersh@redhat.com \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=chen.dylane@linux.dev \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kernel-patches-bot@fb.com \
    --cc=kerneljasonxing@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=leon.hwang@linux.dev \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=rongtao@cestc.cn \
    --cc=sdf@fomichev.me \
    --cc=sforshee@kernel.org \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=willemb@google.com \
    --cc=yatsenko@meta.com \
    --cc=yonghong.song@linux.dev \
    --cc=yuichtsu@amazon.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