From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
delyank@fb.com, acme@redhat.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org
Subject: Re: [PATCH] bpftool: Fix generated code in codegen_asserts
Date: Tue, 29 Mar 2022 02:20:12 +0000 [thread overview]
Message-ID: <164852041246.3757.13606158297445686435.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220328083703.2880079-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 28 Mar 2022 10:37:03 +0200 you wrote:
> Arnaldo reported perf compilation fail with:
>
> $ make -k BUILD_BPF_SKEL=1 CORESIGHT=1 PYTHON=python3
> ...
> In file included from util/bpf_counter.c:28:
> /tmp/build/perf//util/bpf_skel/bperf_leader.skel.h: In function ‘bperf_leader_bpf__assert’:
> /tmp/build/perf//util/bpf_skel/bperf_leader.skel.h:351:51: error: unused parameter ‘s’ [-Werror=unused-parameter]
> 351 | bperf_leader_bpf__assert(struct bperf_leader_bpf *s)
> | ~~~~~~~~~~~~~~~~~~~~~~~~~^
> cc1: all warnings being treated as errors
>
> [...]
Here is the summary with links:
- bpftool: Fix generated code in codegen_asserts
https://git.kernel.org/bpf/bpf/c/ef8a257b4e49
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:[~2022-03-29 2:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 8:37 [PATCH] bpftool: Fix generated code in codegen_asserts Jiri Olsa
2022-03-28 14:57 ` Arnaldo Carvalho de Melo
2022-03-28 15:41 ` Yonghong Song
2022-03-28 18:50 ` Jiri Olsa
2022-03-28 21:31 ` Andrii Nakryiko
2022-03-28 22:53 ` Yonghong Song
2022-03-29 2: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=164852041246.3757.13606158297445686435.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@redhat.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=delyank@fb.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@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;
as well as URLs for NNTP newsgroup(s).