BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@kernel.org, kernel-team@meta.com, naveen@kernel.org
Subject: Re: [PATCH bpf-next] libbpf: fix powerpc's stack register definition in bpf_tracing.h
Date: Thu, 23 Oct 2025 18:30:12 +0000	[thread overview]
Message-ID: <176124421252.3200573.3750075512025000623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251020203643.989467-1-andrii@kernel.org>

Hello:

This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Mon, 20 Oct 2025 13:36:43 -0700 you wrote:
> retsnoop's build on powerpc (ppc64le) architecture ([0]) failed due to
> wrong definition of PT_REGS_SP() macro. Looking at powerpc's
> implementation of stack unwinding in perf_callchain_user_64() clearly
> shows that stack pointer register is gpr[1].
> 
> Fix libbpf's definition of __PT_SP_REG for powerpc to fix all this.
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: fix powerpc's stack register definition in bpf_tracing.h
    https://git.kernel.org/bpf/bpf/c/7221b9caf84b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-10-23 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 20:36 [PATCH bpf-next] libbpf: fix powerpc's stack register definition in bpf_tracing.h Andrii Nakryiko
2025-10-23 14:57 ` Naveen N Rao
2025-10-23 18: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=176124421252.3200573.3750075512025000623.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=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=naveen@kernel.org \
    /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