From: patchwork-bot+netdevbpf@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com, arnd@arndb.de,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
kpsingh@kernel.org, shung-hsi.yu@suse.com, memxor@gmail.com,
davemarchevsky@fb.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bpf: fix perf_snapshot_branch_stack link failure
Date: Fri, 05 Apr 2024 15:50:29 +0000 [thread overview]
Message-ID: <171233222934.27726.10866961945362995147.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240405142637.577046-1-arnd@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 5 Apr 2024 16:26:25 +0200 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The newly added code to handle bpf_get_branch_snapshot fails to link when
> CONFIG_PERF_EVENTS is disabled:
>
> aarch64-linux-ld: kernel/bpf/verifier.o: in function `do_misc_fixups':
> verifier.c:(.text+0x1090c): undefined reference to `__SCK__perf_snapshot_branch_stack'
>
> [...]
Here is the summary with links:
- bpf: fix perf_snapshot_branch_stack link failure
https://git.kernel.org/bpf/bpf-next/c/58babe27180c
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:[~2024-04-05 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 14:26 [PATCH] bpf: fix perf_snapshot_branch_stack link failure Arnd Bergmann
2024-04-05 15:50 ` 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=171233222934.27726.10866961945362995147.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shung-hsi.yu@suse.com \
--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