From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, masahiroy@kernel.org, sdf@fomichev.me
Subject: Re: [PATCH bpf v3] samples/bpf: remove unnecessary -I flags from libbpf EXTRA_CFLAGS
Date: Tue, 03 Dec 2024 22:20:30 +0000 [thread overview]
Message-ID: <173326443030.283880.11574146958380866981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241203182222.3915763-1-eddyz87@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 3 Dec 2024 10:22:22 -0800 you wrote:
> Commit [0] breaks samples/bpf build:
>
> $ make M=samples/bpf
> ...
> make -C /path/to/kernel/samples/bpf/../../tools/lib/bpf \
> ...
> EXTRA_CFLAGS=" \
> ...
> -fsanitize=bounds \
> -I/path/to/kernel/usr/include \
> ...
> /path/to/kernel/samples/bpf/libbpf/libbpf.a install_headers
> CC /path/to/kernel/samples/bpf/libbpf/staticobjs/libbpf.o
> In file included from libbpf.c:29:
> /path/to/kernel/tools/include/linux/err.h:35:8: error: 'inline' can only appear on functions
> 35 | static inline void * __must_check ERR_PTR(long error_)
> | ^
>
> [...]
Here is the summary with links:
- [bpf,v3] samples/bpf: remove unnecessary -I flags from libbpf EXTRA_CFLAGS
https://git.kernel.org/bpf/bpf/c/5a6ea7022ff4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-12-03 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 18:22 [PATCH bpf v3] samples/bpf: remove unnecessary -I flags from libbpf EXTRA_CFLAGS Eduard Zingerman
2024-12-03 22:20 ` patchwork-bot+netdevbpf [this message]
2024-12-04 9:41 ` Viktor Malik
2024-12-04 17:13 ` Eduard Zingerman
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=173326443030.283880.11574146958380866981.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@fb.com \
--cc=martin.lau@linux.dev \
--cc=masahiroy@kernel.org \
--cc=sdf@fomichev.me \
--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