From: patchwork-bot+netdevbpf@kernel.org
To: Hao Luo <haoluo@google.com>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
netdev@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, kpsingh@kernel.org, john.fastabend@gmail.com,
jolsa@kernel.org, sdf@google.com, yosryahmed@google.com
Subject: Re: [PATCH bpf-next v2] bpf: Add CGROUP prefix to cgroup_iter_order
Date: Thu, 25 Aug 2022 23:30:14 +0000 [thread overview]
Message-ID: <166147021499.17452.10347661300375640851.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220825223936.1865810-1-haoluo@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <kafai@fb.com>:
On Thu, 25 Aug 2022 15:39:36 -0700 you wrote:
> bpf_cgroup_iter_order is globally visible but the entries do not have
> CGROUP prefix. As requested by Andrii, put a CGROUP in the names
> in bpf_cgroup_iter_order.
>
> This patch fixes two previous commits: one introduced the API and
> the other uses the API in bpf selftest (that is, the selftest
> cgroup_hierarchical_stats).
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf: Add CGROUP prefix to cgroup_iter_order
https://git.kernel.org/bpf/bpf-next/c/d4ffb6f39f1a
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:[~2022-08-25 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 22:39 [PATCH bpf-next v2] bpf: Add CGROUP prefix to cgroup_iter_order Hao Luo
2022-08-25 23:30 ` 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=166147021499.17452.10347661300375640851.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=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=yosryahmed@google.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