BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kernel-team@fb.com, eddyz87@gmail.com,
	per.xp.sundstrom@ericsson.com
Subject: Re: [PATCH v2 bpf-next 0/6] BTF-to-C dumper fixes and improvements
Date: Wed, 14 Dec 2022 23:10:17 +0000	[thread overview]
Message-ID: <167105941758.13017.10011652519415863225.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221212211505.558851-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Mon, 12 Dec 2022 13:14:59 -0800 you wrote:
> Fix few tricky issues in libbpf's BTF-to-C converter, discovered thanks to
> Per's reports and his randomized testing script.
> 
> Most notably there is a much improved and correct padding handling.  But also
> it turned out that some corner cases with enums weren't handled correctly
> (mode(byte) attribute was a new discovery for me). See respective patches for
> more details.
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,1/6] libbpf: fix single-line struct definition output in btf_dump
    https://git.kernel.org/bpf/bpf-next/c/872aec4b5f63
  - [v2,bpf-next,2/6] libbpf: handle non-standardly sized enums better in BTF-to-C dumper
    https://git.kernel.org/bpf/bpf-next/c/21a9a1bcccaa
  - [v2,bpf-next,3/6] selftests/bpf: add non-standardly sized enum tests for btf_dump
    https://git.kernel.org/bpf/bpf-next/c/9d2349740e43
  - [v2,bpf-next,4/6] libbpf: fix btf__align_of() by taking into account field offsets
    https://git.kernel.org/bpf/bpf-next/c/25a4481b4136
  - [v2,bpf-next,5/6] libbpf: fix BTF-to-C converter's padding logic
    https://git.kernel.org/bpf/bpf-next/c/ea2ce1ba99aa
  - [v2,bpf-next,6/6] selftests/bpf: add few corner cases to test padding handling of btf_dump
    https://git.kernel.org/bpf/bpf-next/c/b148c8b9b926

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-12-14 23:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 21:14 [PATCH v2 bpf-next 0/6] BTF-to-C dumper fixes and improvements Andrii Nakryiko
2022-12-12 21:15 ` [PATCH v2 bpf-next 1/6] libbpf: fix single-line struct definition output in btf_dump Andrii Nakryiko
2022-12-12 21:15 ` [PATCH v2 bpf-next 2/6] libbpf: handle non-standardly sized enums better in BTF-to-C dumper Andrii Nakryiko
2022-12-12 21:15 ` [PATCH v2 bpf-next 3/6] selftests/bpf: add non-standardly sized enum tests for btf_dump Andrii Nakryiko
2022-12-12 21:15 ` [PATCH v2 bpf-next 4/6] libbpf: fix btf__align_of() by taking into account field offsets Andrii Nakryiko
2022-12-12 21:15 ` [PATCH v2 bpf-next 5/6] libbpf: fix BTF-to-C converter's padding logic Andrii Nakryiko
2022-12-15  0:19   ` Eduard Zingerman
2022-12-15  0:34     ` Andrii Nakryiko
2022-12-12 21:15 ` [PATCH v2 bpf-next 6/6] selftests/bpf: add few corner cases to test padding handling of btf_dump Andrii Nakryiko
2022-12-14 23:10 ` 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=167105941758.13017.10011652519415863225.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=eddyz87@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=per.xp.sundstrom@ericsson.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