BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Daniel_M=C3=BCller_=3Cdeso=40posteo=2Enet=3E?=@ci.codeaurora.org
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] libbpf: Support PPC in arch_specific_syscall_pfx
Date: Thu, 28 Jul 2022 23:20:13 +0000	[thread overview]
Message-ID: <165905041359.3277.15995978278460614122.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220728222345.3125975-1-deso@posteo.net>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Thu, 28 Jul 2022 22:23:45 +0000 you wrote:
> Commit 708ac5bea0ce ("libbpf: add ksyscall/kretsyscall sections support
> for syscall kprobes") added the arch_specific_syscall_pfx() function,
> which returns a string representing the architecture in use. As it turns
> out this function is currently not aware of Power PC, where NULL is
> returned. That's being flagged by the libbpf CI system, which builds for
> ppc64le and the compiler sees a NULL pointer being passed in to a %s
> format string.
> With this change we add representations for two more architectures, for
> Power PC and Power PC 64, and also adjust the string format logic to
> handle NULL pointers gracefully, in an attempt to prevent similar issues
> with other architectures in the future.
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: Support PPC in arch_specific_syscall_pfx
    https://git.kernel.org/bpf/bpf-next/c/64893e83f916

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



      reply	other threads:[~2022-07-28 23:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 22:23 [PATCH bpf-next] libbpf: Support PPC in arch_specific_syscall_pfx Daniel Müller
2022-07-28 23: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=165905041359.3277.15995978278460614122.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?Daniel_M=C3=BCller_=3Cdeso=40posteo=2Enet=3E?=@ci.codeaurora.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.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