public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kui-Feng Lee <thinker.li@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
	song@kernel.org, kernel-team@meta.com, andrii@kernel.org,
	eddyz87@gmail.com, sinquersw@gmail.com, kuifeng@meta.com
Subject: Re: [PATCH bpf-next v7 0/9] Enable BPF programs to declare arrays of kptr, bpf_rb_root, and bpf_list_head.
Date: Tue, 04 Jun 2024 04:10:35 +0000	[thread overview]
Message-ID: <171747423536.12524.18107918763541831213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240523174202.461236-1-thinker.li@gmail.com>

Hello:

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

On Thu, 23 May 2024 10:41:53 -0700 you wrote:
> Some types, such as type kptr, bpf_rb_root, and bpf_list_head, are
> treated in a special way. Previously, these types could not be the
> type of a field in a struct type that is used as the type of a global
> variable. They could not be the type of a field in a struct type that
> is used as the type of a field in the value type of a map either. They
> could not even be the type of array elements. This means that they can
> only be the type of global variables or of direct fields in the value
> type of a map.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v7,1/9] bpf: Remove unnecessary checks on the offset of btf_field.
    https://git.kernel.org/bpf/bpf-next/c/c95a3be45ad2
  - [bpf-next,v7,2/9] bpf: Remove unnecessary call to btf_field_type_size().
    https://git.kernel.org/bpf/bpf-next/c/482f7133791e
  - [bpf-next,v7,3/9] bpf: refactor btf_find_struct_field() and btf_find_datasec_var().
    https://git.kernel.org/bpf/bpf-next/c/a7db0d4f872a
  - [bpf-next,v7,4/9] bpf: create repeated fields for arrays.
    https://git.kernel.org/bpf/bpf-next/c/994796c0256c
  - [bpf-next,v7,5/9] bpf: look into the types of the fields of a struct type recursively.
    https://git.kernel.org/bpf/bpf-next/c/64e8ee814819
  - [bpf-next,v7,6/9] bpf: limit the number of levels of a nested struct type.
    https://git.kernel.org/bpf/bpf-next/c/f19caf57d80f
  - [bpf-next,v7,7/9] selftests/bpf: Test kptr arrays and kptrs in nested struct fields.
    https://git.kernel.org/bpf/bpf-next/c/c4c6c3b785a0
  - [bpf-next,v7,8/9] selftests/bpf: Test global bpf_rb_root arrays and fields in nested struct types.
    https://git.kernel.org/bpf/bpf-next/c/d55c765a9b2d
  - [bpf-next,v7,9/9] selftests/bpf: Test global bpf_list_head arrays.
    https://git.kernel.org/bpf/bpf-next/c/43d50ffb1f7e

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-06-04  4:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 17:41 [PATCH bpf-next v7 0/9] Enable BPF programs to declare arrays of kptr, bpf_rb_root, and bpf_list_head Kui-Feng Lee
2024-05-23 17:41 ` [PATCH bpf-next v7 1/9] bpf: Remove unnecessary checks on the offset of btf_field Kui-Feng Lee
2024-05-23 17:41 ` [PATCH bpf-next v7 2/9] bpf: Remove unnecessary call to btf_field_type_size() Kui-Feng Lee
2024-05-23 17:41 ` [PATCH bpf-next v7 3/9] bpf: refactor btf_find_struct_field() and btf_find_datasec_var() Kui-Feng Lee
2024-05-23 17:41 ` [PATCH bpf-next v7 4/9] bpf: create repeated fields for arrays Kui-Feng Lee
2024-05-23 17:41 ` [PATCH bpf-next v7 5/9] bpf: look into the types of the fields of a struct type recursively Kui-Feng Lee
2024-05-23 17:41 ` [PATCH bpf-next v7 6/9] bpf: limit the number of levels of a nested struct type Kui-Feng Lee
2024-05-23 17:42 ` [PATCH bpf-next v7 7/9] selftests/bpf: Test kptr arrays and kptrs in nested struct fields Kui-Feng Lee
2024-05-23 17:42 ` [PATCH bpf-next v7 8/9] selftests/bpf: Test global bpf_rb_root arrays and fields in nested struct types Kui-Feng Lee
2024-05-23 17:42 ` [PATCH bpf-next v7 9/9] selftests/bpf: Test global bpf_list_head arrays Kui-Feng Lee
2024-06-04  4:10 ` 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=171747423536.12524.18107918763541831213.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=eddyz87@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=kuifeng@meta.com \
    --cc=martin.lau@linux.dev \
    --cc=sinquersw@gmail.com \
    --cc=song@kernel.org \
    --cc=thinker.li@gmail.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