[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164455680862.7855.13945335074780551017.git-patchwork-notify@kernel.org>
Date: Fri, 11 Feb 2022 05:20:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Quentin Monnet <quentin@...valent.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [PATCH bpf-next v3 0/2] bpftool: Switch to new versioning scheme
(align on libbpf's)
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Thu, 10 Feb 2022 10:42:35 +0000 you wrote:
> Hi, this set aims at updating the way bpftool versions are numbered.
> Instead of copying the version from the kernel (given that the sources for
> the kernel and bpftool are shipped together), align it on libbpf's version
> number, with a fixed offset (6) to avoid going backwards. Please refer to
> the description of the second commit for details on the motivations.
>
> The patchset also adds the number of the version of libbpf that was used to
> compile to the output of "bpftool version". Bpftool makes such a heavy
> usage of libbpf that it makes sense to indicate what version was used to
> build it.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpftool: Add libbpf's version number to "bpftool version" output
https://git.kernel.org/bpf/bpf-next/c/61fce9693f03
- [bpf-next,v3,2/2] bpftool: Update versioning scheme, align on libbpf's version number
https://git.kernel.org/bpf/bpf-next/c/9910a74d6ebf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists