From: patchwork-bot+netdevbpf@kernel.org
To: Tao Chen <chen.dylane@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, song@kernel.org, houtao1@huawei.com,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [v3 PATCH bpf-next 0/2] bpf: Add percpu map value size check
Date: Wed, 11 Sep 2024 20:30:30 +0000 [thread overview]
Message-ID: <172608663051.1037972.16330226485258580048.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240910144111.1464912-1-chen.dylane@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 10 Sep 2024 22:41:09 +0800 you wrote:
> Check percpu map value size first and add the test case in selftest.
>
> Change list:
> - v2 -> v3:
> - use bpf_map_create API and mv test case in map_percpu_stats.c
> - v1 -> v2:
> - round up map value size with 8 bytes in patch 1
> - add selftest case in patch 2
>
> [...]
Here is the summary with links:
- [v3,bpf-next,1/2] bpf: Check percpu map value size first
https://git.kernel.org/bpf/bpf-next/c/1d244784be6b
- [v3,bpf-next,2/2] bpf/selftests: Check errno when percpu map value size exceeds
https://git.kernel.org/bpf/bpf-next/c/7eab3a58ac7b
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:[~2024-09-11 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 14:41 [v3 PATCH bpf-next 0/2] bpf: Add percpu map value size check Tao Chen
2024-09-10 14:41 ` [v3 PATCH bpf-next 1/2] bpf: Check percpu map value size first Tao Chen
2024-09-10 14:41 ` [v3 PATCH bpf-next 2/2] bpf/selftests: Check errno when percpu map value size exceeds Tao Chen
2024-09-11 20: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=172608663051.1037972.16330226485258580048.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=chen.dylane@gmail.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=houtao1@huawei.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=song@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