From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, venkat88@linux.ibm.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
eddyz87@gmail.com, kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v1] selftests/bpf: Fix arena_spin_lock compilation on PowerPC
Date: Wed, 12 Mar 2025 23:30:32 +0000 [thread overview]
Message-ID: <174182223277.971369.9314488046918159353.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250311154244.3775505-1-memxor@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 11 Mar 2025 08:42:44 -0700 you wrote:
> Venkat reported a compilation error for BPF selftests on PowerPC [0].
> The crux of the error is the following message:
> In file included from progs/arena_spin_lock.c:7:
> /root/bpf-next/tools/testing/selftests/bpf/bpf_arena_spin_lock.h:122:8:
> error: member reference base type '__attribute__((address_space(1)))
> u32' (aka '__attribute__((address_space(1))) unsigned int') is not a
> structure or union
> 122 | old = atomic_read(&lock->val);
>
> [...]
Here is the summary with links:
- [bpf-next,v1] selftests/bpf: Fix arena_spin_lock compilation on PowerPC
https://git.kernel.org/bpf/bpf-next/c/46d38f489ef0
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-03-12 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 15:42 [PATCH bpf-next v1] selftests/bpf: Fix arena_spin_lock compilation on PowerPC Kumar Kartikeya Dwivedi
2025-03-11 15:43 ` Kumar Kartikeya Dwivedi
2025-03-11 18:21 ` Venkat Rao Bagalkote
2025-03-12 23: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=174182223277.971369.9314488046918159353.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=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=venkat88@linux.ibm.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