From: patchwork-bot+netdevbpf@kernel.org
To: David Vernet <void@manifault.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@meta.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
tj@kernel.org, memxor@gmail.com
Subject: Re: [PATCH bpf-next v3 0/7] Enable cpumasks to be used as kptrs
Date: Wed, 25 Jan 2023 16:10:17 +0000 [thread overview]
Message-ID: <167466301762.32537.3494037602376161495.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230125143816.721952-1-void@manifault.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 25 Jan 2023 08:38:09 -0600 you wrote:
> This is part 3 of https://lore.kernel.org/all/20230119235833.2948341-1-void@manifault.com/
>
> Part 2: https://lore.kernel.org/bpf/20230120192523.3650503-1-void@manifault.com/
>
> This series is based off of commit b613d335a743 ("bpf: Allow trusted
> args to walk struct when checking BTF IDs").
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/7] bpf: Disallow NULLable pointers for trusted kfuncs
https://git.kernel.org/bpf/bpf-next/c/caf713c338bd
- [bpf-next,v3,2/7] bpf: Enable cpumasks to be queried and used as kptrs
https://git.kernel.org/bpf/bpf-next/c/516f4d3397c9
- [bpf-next,v3,3/7] selftests/bpf: Add nested trust selftests suite
https://git.kernel.org/bpf/bpf-next/c/a6541f4d2804
- [bpf-next,v3,4/7] selftests/bpf: Add selftest suite for cpumask kfuncs
https://git.kernel.org/bpf/bpf-next/c/7b6abcfa15cd
- [bpf-next,v3,5/7] bpf/docs: Document cpumask kfuncs in a new file
https://git.kernel.org/bpf/bpf-next/c/bdbda395845e
- [bpf-next,v3,6/7] bpf/docs: Document how nested trusted fields may be defined
https://git.kernel.org/bpf/bpf-next/c/d94cbde2183f
- [bpf-next,v3,7/7] bpf/docs: Document the nocast aliasing behavior of ___init
https://git.kernel.org/bpf/bpf-next/c/027bdec89364
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:[~2023-01-25 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 14:38 [PATCH bpf-next v3 0/7] Enable cpumasks to be used as kptrs David Vernet
2023-01-25 14:38 ` [PATCH bpf-next v3 1/7] bpf: Disallow NULLable pointers for trusted kfuncs David Vernet
2023-01-25 14:38 ` [PATCH bpf-next v3 2/7] bpf: Enable cpumasks to be queried and used as kptrs David Vernet
2023-01-25 16:01 ` Alexei Starovoitov
2023-01-25 16:13 ` David Vernet
2023-01-25 14:38 ` [PATCH bpf-next v3 3/7] selftests/bpf: Add nested trust selftests suite David Vernet
2023-01-25 14:38 ` [PATCH bpf-next v3 4/7] selftests/bpf: Add selftest suite for cpumask kfuncs David Vernet
2023-01-25 14:38 ` [PATCH bpf-next v3 5/7] bpf/docs: Document cpumask kfuncs in a new file David Vernet
2023-01-25 14:38 ` [PATCH bpf-next v3 6/7] bpf/docs: Document how nested trusted fields may be defined David Vernet
2023-01-25 14:38 ` [PATCH bpf-next v3 7/7] bpf/docs: Document the nocast aliasing behavior of ___init David Vernet
2023-01-25 16: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=167466301762.32537.3494037602376161495.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.com \
--cc=yhs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox