From: patchwork-bot+netdevbpf@kernel.org
To: Yafang Shao <laoar.shao@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, tj@kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH v4 bpf-next 0/6] bpf: Add support for cgroup1, BPF part
Date: Tue, 14 Nov 2023 17:10:24 +0000 [thread overview]
Message-ID: <169998182491.12736.12381980833332353925.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231111090034.4248-1-laoar.shao@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 11 Nov 2023 09:00:28 +0000 you wrote:
> This is the BPF part of the series "bpf, cgroup: Add BPF support for
> cgroup1 hierarchy" with adjustment in the last two patches compared
> to the previous one.
>
> v3->v4:
> - use subsys_name instead of cgrp_name in get_cgroup_hierarchy_id()
> (Tejun)
> - use local bpf_link instead of modifying the skeleton in the
> selftests
> v3: https://lwn.net/Articles/949264/
>
> [...]
Here is the summary with links:
- [v4,bpf-next,1/6] bpf: Add a new kfunc for cgroup1 hierarchy
https://git.kernel.org/bpf/bpf-next/c/fe977716b40c
- [v4,bpf-next,2/6] selftests/bpf: Fix issues in setup_classid_environment()
https://git.kernel.org/bpf/bpf-next/c/484977558784
- [v4,bpf-next,3/6] selftests/bpf: Add parallel support for classid
https://git.kernel.org/bpf/bpf-next/c/f744d35ecf46
- [v4,bpf-next,4/6] selftests/bpf: Add a new cgroup helper get_classid_cgroup_id()
https://git.kernel.org/bpf/bpf-next/c/c1dcc050aa64
- [v4,bpf-next,5/6] selftests/bpf: Add a new cgroup helper get_cgroup_hierarchy_id()
https://git.kernel.org/bpf/bpf-next/c/bf47300b186f
- [v4,bpf-next,6/6] selftests/bpf: Add selftests for cgroup1 hierarchy
https://git.kernel.org/bpf/bpf-next/c/360769233cc9
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-14 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 9:00 [PATCH v4 bpf-next 0/6] bpf: Add support for cgroup1, BPF part Yafang Shao
2023-11-11 9:00 ` [PATCH v4 bpf-next 1/6] bpf: Add a new kfunc for cgroup1 hierarchy Yafang Shao
2023-11-11 9:00 ` [PATCH v4 bpf-next 2/6] selftests/bpf: Fix issues in setup_classid_environment() Yafang Shao
2023-11-11 9:00 ` [PATCH v4 bpf-next 3/6] selftests/bpf: Add parallel support for classid Yafang Shao
2023-11-11 9:00 ` [PATCH v4 bpf-next 4/6] selftests/bpf: Add a new cgroup helper get_classid_cgroup_id() Yafang Shao
2023-11-11 9:00 ` [PATCH v4 bpf-next 5/6] selftests/bpf: Add a new cgroup helper get_cgroup_hierarchy_id() Yafang Shao
2023-11-11 9:00 ` [PATCH v4 bpf-next 6/6] selftests/bpf: Add selftests for cgroup1 hierarchy Yafang Shao
2023-11-14 17:06 ` Alexei Starovoitov
2023-11-15 1:47 ` Yafang Shao
2023-11-14 17: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=169998182491.12736.12381980833332353925.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=kpsingh@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=yonghong.song@linux.dev \
/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