BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, qmo@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next] bpftool: Strip all -Wformat* flags from bootstrap libbpf build
Date: Wed, 01 Jul 2026 18:20:21 +0000	[thread overview]
Message-ID: <178293002115.1238008.12470076131335703921.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260630205418.3483969-1-andrii@kernel.org>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Tue, 30 Jun 2026 13:54:18 -0700 you wrote:
> Commit 9080b97689db ("bpftool: Pass host flags to bootstrap libbpf")
> started building the bootstrap libbpf with HOST_CFLAGS, stripping the
> warning options that are unsuitable for that build by filtering out
> -W -Wall -Wextra -Wformat -Wformat-signedness.
> 
> HOST_CFLAGS inherits EXTRA_WARNINGS, which includes -Wformat-security
> and -Wformat-y2k. The filter drops -Wall and -Wformat (the latter being
> what actually enables -Wformat), but leaves those two -Wformat-* children
> in LIBBPF_BOOTSTRAP_CFLAGS. Building the bootstrap libbpf with it then
> warns:
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpftool: Strip all -Wformat* flags from bootstrap libbpf build
    https://git.kernel.org/bpf/bpf-next/c/a954c9e3168c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-01 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 20:54 [PATCH bpf-next] bpftool: Strip all -Wformat* flags from bootstrap libbpf build Andrii Nakryiko
2026-07-01 12:53 ` Quentin Monnet
2026-07-01 18:15   ` Andrii Nakryiko
2026-07-02 14:57     ` Quentin Monnet
2026-07-02 16:21       ` Andrii Nakryiko
2026-07-01 18: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=178293002115.1238008.12470076131335703921.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=kernel-team@meta.com \
    --cc=qmo@kernel.org \
    /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