From: patchwork-bot+netdevbpf@kernel.org
To: Quentin Monnet <quentin@isovalent.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
acme@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org,
songliubraving@fb.com, jolsa@kernel.org, namhyung@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf] bpftool: Install libbpf headers for the bootstrap version, too
Date: Fri, 05 Nov 2021 15:30:09 +0000 [thread overview]
Message-ID: <163612620972.29979.8998296341719188720.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211105015813.6171-1-quentin@isovalent.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 5 Nov 2021 01:58:13 +0000 you wrote:
> We recently changed bpftool's Makefile to make it install libbpf's
> headers locally instead of pulling them from the source directory of the
> library. Although bpftool needs two versions of libbpf, a "regular" one
> and a "bootstrap" version, we would only install headers for the regular
> libbpf build. Given that this build always occurs before the bootstrap
> build when building bpftool, this is enough to ensure that the bootstrap
> bpftool will have access to the headers exported through the regular
> libbpf build.
>
> [...]
Here is the summary with links:
- [bpf] bpftool: Install libbpf headers for the bootstrap version, too
https://git.kernel.org/bpf/bpf/c/e41ac2020bca
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:[~2021-11-05 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 1:58 [PATCH bpf] bpftool: Install libbpf headers for the bootstrap version, too Quentin Monnet
2021-11-05 10:55 ` Arnaldo Carvalho de Melo
2021-11-05 10:57 ` Arnaldo Carvalho de Melo
2021-11-05 15:30 ` 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=163612620972.29979.8998296341719188720.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=songliubraving@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.