From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, morbo@google.com,
bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next 0/3] libbpf: btf typed data dumping fixes (__int128 usage, error propagation)
Date: Tue, 20 Jul 2021 21:00:05 +0000 [thread overview]
Message-ID: <162681480523.17696.5006485416633503610.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1626770993-11073-1-git-send-email-alan.maguire@oracle.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 20 Jul 2021 09:49:50 +0100 you wrote:
> This series aims to resolve further issues with the BTF typed data
> dumping interfaces in libbpf.
>
> Compilation failures with use of __int128 on 32-bit platforms were
> reported [1]. As a result, the use of __int128 in libbpf typed data
> dumping is replaced with __u64 usage for bitfield manipulations.
> In the case of 128-bit integer values, they are simply split into
> two 64-bit hex values for display (patch 1).
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/3] libbpf: avoid use of __int128 in typed dump display
https://git.kernel.org/bpf/bpf-next/c/a1d3cc3c5eca
- [v2,bpf-next,2/3] selftests/bpf: add __int128-specific tests for typed data dump
https://git.kernel.org/bpf/bpf-next/c/a17553dde294
- [v2,bpf-next,3/3] libbpf: propagate errors when retrieving enum value for typed data display
https://git.kernel.org/bpf/bpf-next/c/720c29fca9fb
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:[~2021-07-20 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 8:49 [PATCH v2 bpf-next 0/3] libbpf: btf typed data dumping fixes (__int128 usage, error propagation) Alan Maguire
2021-07-20 8:49 ` [PATCH v2 bpf-next 1/3] libbpf: avoid use of __int128 in typed dump display Alan Maguire
2021-07-20 8:49 ` [PATCH v2 bpf-next 2/3] selftests/bpf: add __int128-specific tests for typed data dump Alan Maguire
2021-07-20 8:49 ` [PATCH v2 bpf-next 3/3] libbpf: propagate errors when retrieving enum value for typed data display Alan Maguire
2021-07-20 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=162681480523.17696.5006485416633503610.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=morbo@google.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.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;
as well as URLs for NNTP newsgroup(s).