From: patchwork-bot+netdevbpf@kernel.org
To: Jerome Marchand <jmarchan@redhat.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
memxor@gmail.com, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] samples: bpf: Don't fail for a missing VMLINUX_BTF when VMLINUX_H is provided
Date: Tue, 10 May 2022 00:50:12 +0000 [thread overview]
Message-ID: <165214381239.1602.1018932987303312053.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220507161635.2219052-1-jmarchan@redhat.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sat, 7 May 2022 18:16:35 +0200 you wrote:
> samples/bpf build currently always fails if it can't generate
> vmlinux.h from vmlinux, even when vmlinux.h is directly provided by
> VMLINUX_H variable, which makes VMLINUX_H pointless.
> Only fails when neither method works.
>
> Fixes: 384b6b3bbf0d ("samples: bpf: Add vmlinux.h generation support")
> Reported-by: CKI Project <cki-project@redhat.com>
> Reported-by: Veronika Kabatova <vkabatov@redhat.com>
> Signed-off-by: Jerome Marchand <jmarchan@redhat.com>
>
> [...]
Here is the summary with links:
- samples: bpf: Don't fail for a missing VMLINUX_BTF when VMLINUX_H is provided
https://git.kernel.org/bpf/bpf-next/c/ec24704492d8
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:[~2022-05-10 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 16:16 [PATCH] samples: bpf: Don't fail for a missing VMLINUX_BTF when VMLINUX_H is provided Jerome Marchand
2022-05-10 0:50 ` 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=165214381239.1602.1018932987303312053.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=jmarchan@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.