Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH bpf] bpftool: Install libbpf headers for the bootstrap
 version, too
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <163612620972.29979.8998296341719188720.git-patchwork-notify@kernel.org>
Date:   Fri, 05 Nov 2021 15:30:09 +0000
References: <20211105015813.6171-1-quentin@isovalent.com>
In-Reply-To: <20211105015813.6171-1-quentin@isovalent.com>
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
Precedence: bulk

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