From: patchwork-bot+netdevbpf@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, alan.maguire@oracle.com,
pulehui@huawei.com
Subject: Re: [PATCH bpf-next] kbuild, bpf: Correct pahole version that supports distilled base btf feature
Date: Mon, 24 Feb 2025 22:20:33 +0000 [thread overview]
Message-ID: <174043563304.3628285.11966484526881480198.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250219063113.706600-1-pulehui@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 19 Feb 2025 06:31:13 +0000 you wrote:
> From: Pu Lehui <pulehui@huawei.com>
>
> pahole commit [0] of supporting distilled base btf feature released on
> pahole v1.28 rather than v1.26. So let's correct this.
>
> Link: https://git.kernel.org/pub/scm/devel/pahole/pahole.git/commit/?id=c7b1f6a29ba1 [0]
> Signed-off-by: Pu Lehui <pulehui@huawei.com>
>
> [...]
Here is the summary with links:
- [bpf-next] kbuild, bpf: Correct pahole version that supports distilled base btf feature
https://git.kernel.org/bpf/bpf-next/c/1ffe30efd2f2
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:[~2025-02-24 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 6:31 [PATCH bpf-next] kbuild, bpf: Correct pahole version that supports distilled base btf feature Pu Lehui
2025-02-21 0:30 ` Andrii Nakryiko
2025-02-24 12:16 ` Pu Lehui
2025-02-24 22:24 ` Andrii Nakryiko
2025-02-25 9:32 ` Alan Maguire
2025-02-24 22:20 ` 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=174043563304.3628285.11966484526881480198.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox