From: patchwork-bot+netdevbpf@kernel.org
To: Tao Chen <chen.dylane@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] samples: bpf: Add valid info for VMLINUX_BTF
Date: Mon, 29 Apr 2024 23:20:30 +0000 [thread overview]
Message-ID: <171443283043.1398.11744904571177428676.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240428161032.239043-1-chen.dylane@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 29 Apr 2024 00:10:32 +0800 you wrote:
> When i use the command 'make M=samples/bpf' to compile samples/bpf code
> in ubuntu 22.04, the error info occured:
> Cannot find a vmlinux for VMLINUX_BTF at any of " /home/ubuntu/code/linux/vmlinux",
> build the kernel or set VMLINUX_BTF or VMLINUX_H variable
>
> Others often encounter this kind of issue, new kernel has the vmlinux, so we can
> set the path in error info which seems more intuitive, like:
> Cannot find a vmlinux for VMLINUX_BTF at any of " /home/ubuntu/code/linux/vmlinux",
> buiild the kernel or set VMLINUX_BTF like "VMLINUX_BTF=/sys/kernel/btf/vmlinux" or
> VMLINUX_H variable
>
> [...]
Here is the summary with links:
- samples: bpf: Add valid info for VMLINUX_BTF
https://git.kernel.org/bpf/bpf-next/c/397658ddc88c
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:[~2024-04-29 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 16:10 [PATCH] samples: bpf: Add valid info for VMLINUX_BTF Tao Chen
2024-04-29 23: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=171443283043.1398.11744904571177428676.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=chen.dylane@gmail.com \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).