From: patchwork-bot+netdevbpf@kernel.org
To: Chuyi Zhou <zhouchuyi@bytedance.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v4 0/3] Relax allowlist for open-coded css_task iter
Date: Thu, 02 Nov 2023 06:10:24 +0000 [thread overview]
Message-ID: <169890542463.15699.9328828031519896553.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231031050438.93297-1-zhouchuyi@bytedance.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 31 Oct 2023 13:04:35 +0800 you wrote:
> Hi,
> The patchset aims to relax the allowlist for open-coded css_task iter
> suggested by Alexei[1].
>
> Please see individual patches for more details. And comments are always
> welcome.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/3] bpf: Relax allowlist for css_task iter
https://git.kernel.org/bpf/bpf/c/3091b667498b
- [bpf-next,v4,2/3] selftests/bpf: Add tests for css_task iter combining with cgroup iter
https://git.kernel.org/bpf/bpf/c/f49843afde67
- [bpf-next,v4,3/3] selftests/bpf: Add test for using css_task iter in sleepable progs
https://git.kernel.org/bpf/bpf/c/d8234d47c4aa
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-11-02 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 5:04 [PATCH bpf-next v4 0/3] Relax allowlist for open-coded css_task iter Chuyi Zhou
2023-10-31 5:04 ` [PATCH bpf-next v4 1/3] bpf: Relax allowlist for " Chuyi Zhou
2023-10-31 5:04 ` [PATCH bpf-next v4 2/3] selftests/bpf: Add tests for css_task iter combining with cgroup iter Chuyi Zhou
2023-10-31 5:04 ` [PATCH bpf-next v4 3/3] selftests/bpf: Add test for using css_task iter in sleepable progs Chuyi Zhou
2023-11-02 2:52 ` Yonghong Song
2023-11-02 6: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=169890542463.15699.9328828031519896553.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=zhouchuyi@bytedance.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