Dwarves debugging tools
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
	yonghong.song@linux.dev, jolsa@kernel.org, qmo@kernel.org,
	ihor.solodrai@linux.dev, mykyta.yatsenko5@gmail.com,
	dwarves@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v16 bpf-next 0/9] Add BTF layout to BTF
Date: Thu, 26 Mar 2026 21:20:26 +0000	[thread overview]
Message-ID: <177456002639.3181880.17500353700750230925.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260326145444.2076244-1-alan.maguire@oracle.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Thu, 26 Mar 2026 14:54:35 +0000 you wrote:
> Update struct btf_header to add a new "layout" section containing
> a description of how to parse the BTF kinds known about at BTF
> encoding time.  This provides the opportunity for tools that might
> not know all of these kinds - as is the case when older tools run
> on more newly-generated BTF - to still parse the BTF provided,
> even if it cannot all be used.
> 
> [...]

Here is the summary with links:
  - [v16,bpf-next,1/9] btf: Add BTF kind layout encoding to UAPI
    https://git.kernel.org/bpf/bpf-next/c/222edc843c15
  - [v16,bpf-next,2/9] libbpf: Support layout section handling in BTF
    https://git.kernel.org/bpf/bpf-next/c/087f3964f4b3
  - [v16,bpf-next,3/9] libbpf: Use layout to compute an unknown kind size
    https://git.kernel.org/bpf/bpf-next/c/2ecbe53e0e99
  - [v16,bpf-next,4/9] libbpf: Add layout encoding support
    https://git.kernel.org/bpf/bpf-next/c/d686d92c4080
  - [v16,bpf-next,5/9] libbpf: BTF validation can use layout for unknown kinds
    https://git.kernel.org/bpf/bpf-next/c/6ad89285996a
  - [v16,bpf-next,6/9] libbpf: Support sanitization of BTF layout for older kernels
    https://git.kernel.org/bpf/bpf-next/c/081677d03d8b
  - [v16,bpf-next,7/9] btf: support kernel parsing of BTF with layout info
    https://git.kernel.org/bpf/bpf-next/c/626e88c070ee
  - [v16,bpf-next,8/9] selftests/bpf: Test kind encoding/decoding
    https://git.kernel.org/bpf/bpf-next/c/0467491617cb
  - [v16,bpf-next,9/9] kbuild, bpf: Specify "layout" optional feature
    https://git.kernel.org/bpf/bpf-next/c/5e1942eb1c01

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



      parent reply	other threads:[~2026-03-26 21:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 14:54 [PATCH v16 bpf-next 0/9] Add BTF layout to BTF Alan Maguire
2026-03-26 14:54 ` [PATCH v16 bpf-next 1/9] btf: Add BTF kind layout encoding to UAPI Alan Maguire
2026-03-26 15:53   ` bot+bpf-ci
2026-03-26 14:54 ` [PATCH v16 bpf-next 2/9] libbpf: Support layout section handling in BTF Alan Maguire
2026-03-26 14:54 ` [PATCH v16 bpf-next 3/9] libbpf: Use layout to compute an unknown kind size Alan Maguire
2026-03-26 14:54 ` [PATCH v16 bpf-next 4/9] libbpf: Add layout encoding support Alan Maguire
2026-03-26 14:54 ` [PATCH v16 bpf-next 5/9] libbpf: BTF validation can use layout for unknown kinds Alan Maguire
2026-03-26 14:54 ` [PATCH v16 bpf-next 6/9] libbpf: Support sanitization of BTF layout for older kernels Alan Maguire
2026-03-26 14:54 ` [PATCH v16 bpf-next 7/9] btf: support kernel parsing of BTF with layout info Alan Maguire
2026-03-26 14:54 ` [PATCH v16 bpf-next 8/9] selftests/bpf: Test kind encoding/decoding Alan Maguire
2026-03-26 14:54 ` [PATCH v16 bpf-next 9/9] kbuild, bpf: Specify "layout" optional feature Alan Maguire
2026-03-26 21:20 ` 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=177456002639.3181880.17500353700750230925.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=dwarves@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=qmo@kernel.org \
    --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