From: patchwork-bot+netdevbpf@kernel.org
To: Hungyu Lin <dennylin0707@gmail.com>
Cc: ast@kernel.org, bpf@vger.kernel.org, andrii@kernel.org,
qmo@kernel.org, daniel@iogearbox.net, yonghong.song@linux.dev,
eddyz87@gmail.com, ihor.solodrai@linux.dev, shuah@kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v5 0/3] Normalize enum values in libbpf and bpftool
Date: Thu, 12 Nov 2026 21:00:09 +0000 [thread overview]
Message-ID: <179451720953.643214.15898220992181188429.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261108025632.10799-1-dennylin0707@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 8 Nov 2026 02:56:29 +0000 you wrote:
> This series fixes enum signedness in libbpf and bpftool data dumps
> using the shared btf_enum_value() helper suggested by Alexei. It also
> uses the helper for enum-backed map fields, where sign extension can
> change the requested map_extra value.
>
> Ordinary enums are interpreted according to kflag. When kflag is
> clear, values are treated as unsigned, including BTF from producers
> that did not record signedness.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/3] libbpf: Normalize enum values according to signedness
https://git.kernel.org/bpf/bpf-next/c/89e7a42e3030
- [bpf-next,v5,2/3] bpftool: Preserve unsigned enum values in data dumps
https://git.kernel.org/bpf/bpf-next/c/0296813e0c59
- [bpf-next,v5,3/3] selftests/bpf: Cover enum signedness in data dumps and map fields
https://git.kernel.org/bpf/bpf-next/c/881dbe78cc98
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:[~2026-11-12 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 2:56 Hungyu Lin
2026-11-08 2:56 ` [PATCH bpf-next v5 1/3] libbpf: Normalize enum values according to signedness Hungyu Lin
2026-11-08 2:56 ` [PATCH bpf-next v5 2/3] bpftool: Preserve unsigned enum values in data dumps Hungyu Lin
2026-11-08 2:56 ` [PATCH bpf-next v5 3/3] selftests/bpf: Cover enum signedness in data dumps and map fields Hungyu Lin
2026-11-12 21:00 ` 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=179451720953.643214.15898220992181188429.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=dennylin0707@gmail.com \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=qmo@kernel.org \
--cc=shuah@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
all inboxes | Powered by JetHome®