From: patchwork-bot+netdevbpf@kernel.org
To: Hao Xiang <hao.xiang@bytedance.com>
Cc: bpf@vger.kernel.org, horenchuang@bytedance.com
Subject: Re: [PATCH bpf-next v5 1/1] libbpf: Correctly set the kernel code version in Debian kernel.
Date: Mon, 06 Feb 2023 22:40:17 +0000 [thread overview]
Message-ID: <167572321717.17917.7525968332821642999.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230203234842.2933903-1-hao.xiang@bytedance.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 3 Feb 2023 23:48:42 +0000 you wrote:
> In a previous commit, Ubuntu kernel code version is correctly set
> by retrieving the information from /proc/version_signature.
>
> commit<5b3d72987701d51bf31823b39db49d10970f5c2d>
> (libbpf: Improve LINUX_VERSION_CODE detection)
>
> The /proc/version_signature file doesn't present in at least the
> older versions of Debian distributions (eg, Debian 9, 10). The Debian
> kernel has a similar issue where the release information from uname()
> syscall doesn't give the kernel code version that matches what the
> kernel actually expects. Below is an example content from Debian 10.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/1] libbpf: Correctly set the kernel code version in Debian kernel.
https://git.kernel.org/bpf/bpf-next/c/d1d7730ff875
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:[~2023-02-06 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 23:48 [PATCH bpf-next v5 1/1] libbpf: Correctly set the kernel code version in Debian kernel Hao Xiang
2023-02-06 22:40 ` 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=167572321717.17917.7525968332821642999.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=hao.xiang@bytedance.com \
--cc=horenchuang@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox