From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Lobakin <alexandr.lobakin@intel.com>
Cc: ast@kernel.org, daniel@iogearbox.net, jesse.brandeburg@intel.com,
maciej.fijalkowski@intel.com, michal.swiatkowski@linux.intel.com,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
nathan@kernel.org, ndesaulniers@google.com, adobriyan@gmail.com,
masahiroy@kernel.org, ardb@kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH bpf] samples: bpf: fix build error due to -isystem removal
Date: Mon, 15 Nov 2021 23:00:09 +0000 [thread overview]
Message-ID: <163701720943.28601.12990584204511867827.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211115130741.3584-1-alexandr.lobakin@intel.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 15 Nov 2021 14:07:41 +0100 you wrote:
> Since recent Kbuild updates we no longer include files from compiler
> directories. However, samples/bpf/hbm_kern.h hasn't been tuned for
> this (LLVM 13):
>
> CLANG-bpf samples/bpf/hbm_out_kern.o
> In file included from samples/bpf/hbm_out_kern.c:55:
> samples/bpf/hbm_kern.h:12:10: fatal error: 'stddef.h' file not found
> ^~~~~~~~~~
> 1 error generated.
> CLANG-bpf samples/bpf/hbm_edt_kern.o
> In file included from samples/bpf/hbm_edt_kern.c:53:
> samples/bpf/hbm_kern.h:12:10: fatal error: 'stddef.h' file not found
> ^~~~~~~~~~
> 1 error generated.
>
> [...]
Here is the summary with links:
- [bpf] samples: bpf: fix build error due to -isystem removal
https://git.kernel.org/bpf/bpf/c/6e528ca494d4
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:[~2021-11-16 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 13:07 Alexander Lobakin
2021-11-15 23:00 ` 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=163701720943.28601.12990584204511867827.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=adobriyan@gmail.com \
--cc=alexandr.lobakin@intel.com \
--cc=andrii@kernel.org \
--cc=ardb@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jesse.brandeburg@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=maciej.fijalkowski@intel.com \
--cc=masahiroy@kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--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
Powered by JetHome