From: patchwork-bot+netdevbpf@kernel.org
To: Vineet Gupta <vineet.gupta@linux.dev>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] selftests/bpf: Fix linked_externs with bpf-gcc
Date: Tue, 29 Sep 2026 00:30:04 +0000 [thread overview]
Message-ID: <179064180465.191583.15471520718506070506.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928231441.4037097-1-vineet.gupta@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 28 Sep 2026 16:14:41 -0700 you wrote:
> test_progs-bpf_gcc fails to build:
>
> prog_tests/linked_externs.c:17:23: error: 'struct linked_arena' has no
> member named 'arena'
>
> Several problems, all from bpf-gcc not supporting address_space(1).
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: Fix linked_externs with bpf-gcc
https://git.kernel.org/bpf/bpf-next/c/61c1e63c9b65
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-29 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 23:14 [PATCH bpf-next v2] selftests/bpf: Fix linked_externs with bpf-gcc Vineet Gupta
2026-09-29 0:01 ` Ihor Solodrai
2026-09-29 0:26 ` Andrii Nakryiko
2026-09-29 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=179064180465.191583.15471520718506070506.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=vineet.gupta@linux.dev \
--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.