From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com, naresh.kamboju@linaro.org,
sfr@canb.auug.org.au
Subject: Re: [PATCH bpf-next] libbpf: fix use #ifdef instead of #if to avoid compiler warning
Date: Thu, 07 Apr 2022 21:40:12 +0000 [thread overview]
Message-ID: <164936761240.22211.4406395532419744389.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220407203842.3019904-1-andrii@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 7 Apr 2022 13:38:42 -0700 you wrote:
> As reported by Naresh:
>
> perf build errors on i386 [1] on Linux next-20220407 [2]
>
> usdt.c:1181:5: error: "__x86_64__" is not defined, evaluates to 0
> [-Werror=undef]
> 1181 | #if __x86_64__
> | ^~~~~~~~~~
> usdt.c:1196:5: error: "__x86_64__" is not defined, evaluates to 0
> [-Werror=undef]
> 1196 | #if __x86_64__
> | ^~~~~~~~~~
> cc1: all warnings being treated as errors
>
> [...]
Here is the summary with links:
- [bpf-next] libbpf: fix use #ifdef instead of #if to avoid compiler warning
https://git.kernel.org/bpf/bpf-next/c/ded6dffaed5e
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-04-07 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 20:38 [PATCH bpf-next] libbpf: fix use #ifdef instead of #if to avoid compiler warning Andrii Nakryiko
2022-04-07 21:40 ` 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=164936761240.22211.4406395532419744389.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=kernel-team@fb.com \
--cc=naresh.kamboju@linaro.org \
--cc=sfr@canb.auug.org.au \
/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