Received-SPF: pass (google.com: domain of linux-kernel+bounces-43695-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v3] libbpf: Add some details for BTF parsing failures
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <170657582471.7562.5549307900236882760.git-patchwork-notify@kernel.org>
Date: Tue, 30 Jan 2024 00:50:24 +0000
References: <20240125231840.1647951-1-irogers@google.com>
In-Reply-To: <20240125231840.1647951-1-irogers@google.com>
To: Ian Rogers <irogers@google.com>
Cc: alan.maguire@oracle.com, ast@kernel.org, daniel@iogearbox.net,
 andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
 yonghong.song@linux.dev, john.fastabend@gmail.com, kpsingh@kernel.org,
 sdf@google.com, haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org,
 linux-kernel@vger.kernel.org

Hello:

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

On Thu, 25 Jan 2024 15:18:40 -0800 you wrote:
> As CONFIG_DEBUG_INFO_BTF is default off the existing "failed to find
> valid kernel BTF" message makes diagnosing the kernel build issue some
> what cryptic. Add a little more detail with the hope of helping users.
> 
> Before:
> ```
> libbpf: failed to find valid kernel BTF
> libbpf: Error loading vmlinux BTF: -3
> ```
> 
> [...]

Here is the summary with links:
  - [v3] libbpf: Add some details for BTF parsing failures
    https://git.kernel.org/bpf/bpf-next/c/f2e4040c82d3

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