From: patchwork-bot+netdevbpf@kernel.org
To: Tejun Heo <tj@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org,
davemarchevsky@meta.com, void@manifault.com,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2 1/2 bpf-next] bpf: Add bpf_cgroup_from_id() kfunc
Date: Thu, 23 Feb 2023 16:40:18 +0000 [thread overview]
Message-ID: <167717041811.11071.10181818674097772190.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Y/bBaG96t0/gQl9/@slm.duckdns.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 22 Feb 2023 15:29:12 -1000 you wrote:
> cgroup ID is an userspace-visible 64bit value uniquely identifying a given
> cgroup. As the IDs are used widely, it's useful to be able to look up the
> matching cgroups. Add bpf_cgroup_from_id().
>
> v2: Separate out selftest into its own patch as suggested by Alexei.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
>
> [...]
Here is the summary with links:
- [v2,1/2,bpf-next] bpf: Add bpf_cgroup_from_id() kfunc
https://git.kernel.org/bpf/bpf-next/c/332ea1f697be
- [v2,2/2,bpf-next] selftests/bpf: Add a test case for bpf_cgroup_from_id()
https://git.kernel.org/bpf/bpf-next/c/d0093aaefa35
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-02-23 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 1:29 [PATCH v2 1/2 bpf-next] bpf: Add bpf_cgroup_from_id() kfunc Tejun Heo
2023-02-23 1:29 ` [PATCH v2 2/2 bpf-next] selftests/bpf: Add a test case for bpf_cgroup_from_id() Tejun Heo
2023-02-23 16:40 ` 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=167717041811.11071.10181818674097772190.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=davemarchevsky@meta.com \
--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=sdf@google.com \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.com \
--cc=yhs@fb.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