From: patchwork-bot+netdevbpf@kernel.org
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, ihor.solodrai@linux.dev,
ast@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libbpf: Fix debian kernel version information parsing
Date: Thu, 03 Sep 2026 00:30:13 +0000 [thread overview]
Message-ID: <178839541365.3016145.3676674062355526441.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260831134537.1227914-1-sudipm.mukherjee@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 31 Aug 2026 14:45:37 +0100 you wrote:
> Currently get_debian_kernel_version() expects the version to be in the
> form of x.y.z but the Debian kernels uploaded to experimental are not
> always LTS kernels. Like the current Debian kernel in experimental
> is 7.2~rc7-1~exp1 and uname -v reported "Debian 7.2~rc7-1~exp1".
>
> Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
>
> [...]
Here is the summary with links:
- libbpf: Fix debian kernel version information parsing
https://git.kernel.org/bpf/bpf-next/c/7bf591f26545
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:[~2026-09-03 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 13:45 [PATCH] libbpf: Fix debian kernel version information parsing Sudip Mukherjee
2026-08-31 14:33 ` bot+bpf-ci
2026-09-03 0: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=178839541365.3016145.3676674062355526441.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=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=yonghong.song@linux.dev \
/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.