From: patchwork-bot+netdevbpf@kernel.org
To: Leo Yan <leo.yan@arm.com>
Cc: qmo@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
lmb@isovalent.com, nathan@kernel.org,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
justinstitt@google.com, acme@kernel.org, namhyung@kernel.org,
irogers@google.com, james.clark@linaro.org, kees@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, llvm@lists.linux.dev,
ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next v2 0/8] tools build: bpf: Append EXTRA_CFLAGS and HOST_EXTRACFLAGS
Date: Mon, 15 Jun 2026 00:40:28 +0000 [thread overview]
Message-ID: <178148402863.2363016.5034665284884003104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260602-tools_build_fix_zero_init_bpf_only-v2-0-c76e5250ea1c@arm.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 02 Jun 2026 15:47:09 +0100 you wrote:
> Append EXTRA_CFLAGS and HOST_EXTRACFLAGS to the BPF build.
>
> This mitigates an issue introduced in GCC 15, where a {0} initializer
> does not guarantee zeroing the entire union [1].
>
> The common changes under tools to support EXTRA_CFLAGS and
> HOST_EXTRACFLAGS are sent separately [2]. As suggested, BPF patches
> would be picked up via the bpf tree, so this series only includes BPF
> related changes.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/8] bpftool: Pass host flags to bootstrap libbpf
https://git.kernel.org/bpf/bpf-next/c/9080b97689db
- [bpf-next,v2,2/8] bpftool: Avoid adding EXTRA_CFLAGS to HOST_CFLAGS
https://git.kernel.org/bpf/bpf-next/c/956841cbc3d7
- [bpf-next,v2,3/8] bpftool: Append extra host flags
https://git.kernel.org/bpf/bpf-next/c/3f2fec5b02b6
- [bpf-next,v2,4/8] libbpf: Initialize CFLAGS before including Makefile.include
https://git.kernel.org/bpf/bpf-next/c/f3846b3800a2
- [bpf-next,v2,5/8] tools/bpf: build: Append extra cflags
https://git.kernel.org/bpf/bpf-next/c/b40ba139371c
- [bpf-next,v2,6/8] selftests/bpf: Initialize operation name before use
https://git.kernel.org/bpf/bpf-next/c/55ffbe8a15b1
- [bpf-next,v2,7/8] selftests/bpf: Use common CFLAGS for urandom_read
https://git.kernel.org/bpf/bpf-next/c/584f3b7a3525
- [bpf-next,v2,8/8] selftests/bpf: Avoid static LLVM linking for cross builds
https://git.kernel.org/bpf/bpf-next/c/62617d28d9ae
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:[~2026-06-15 0:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 14:47 [PATCH bpf-next v2 0/8] tools build: bpf: Append EXTRA_CFLAGS and HOST_EXTRACFLAGS Leo Yan
2026-06-02 14:47 ` [PATCH bpf-next v2 1/8] bpftool: Pass host flags to bootstrap libbpf Leo Yan
2026-06-03 9:21 ` Quentin Monnet
2026-06-02 14:47 ` [PATCH bpf-next v2 2/8] bpftool: Avoid adding EXTRA_CFLAGS to HOST_CFLAGS Leo Yan
2026-06-02 14:47 ` [PATCH bpf-next v2 3/8] bpftool: Append extra host flags Leo Yan
2026-06-02 14:47 ` [PATCH bpf-next v2 4/8] libbpf: Initialize CFLAGS before including Makefile.include Leo Yan
2026-06-02 14:47 ` [PATCH bpf-next v2 5/8] tools/bpf: build: Append extra cflags Leo Yan
2026-06-13 1:09 ` Ihor Solodrai
2026-06-02 14:47 ` [PATCH bpf-next v2 6/8] selftests/bpf: Initialize operation name before use Leo Yan
2026-06-13 1:11 ` Ihor Solodrai
2026-06-02 14:47 ` [PATCH bpf-next v2 7/8] selftests/bpf: Use common CFLAGS for urandom_read Leo Yan
2026-06-02 15:32 ` bot+bpf-ci
2026-06-02 14:47 ` [PATCH bpf-next v2 8/8] selftests/bpf: Avoid static LLVM linking for cross builds Leo Yan
2026-06-15 0: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=178148402863.2363016.5034665284884003104.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=ihor.solodrai@linux.dev \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=kpsingh@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lmb@isovalent.com \
--cc=martin.lau@linux.dev \
--cc=morbo@google.com \
--cc=namhyung@kernel.org \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--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