From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?UmljYXJkbyBCLiBNYXJsacOocmUgPHJibUBzdXNlLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, corbet@lwn.net, skhan@linuxfoundation.org,
bpf@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/bpf: Document BPF_STRICT_BUILD=0 to tolerate test build failures
Date: Mon, 06 Jul 2026 22:30:11 +0000 [thread overview]
Message-ID: <178337701189.1232545.1878877150316891466.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260706-b4-bpf_strict_build_docs-v1-1-5324d605c7b0@suse.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Mon, 06 Jul 2026 12:28:43 -0300 you wrote:
> When the kernel config does not fully match the BPF selftest config
> fragment, some tests may fail to compile. BPF_STRICT_BUILD (defaulting to
> 1) makes any such failure fatal. Mention the option so that developers are
> aware they can set it to 0 to skip broken tests and keep the build going,
> which is particularly useful during bringup or when testing on constrained
> (e.g. distribution) configurations.
>
> [...]
Here is the summary with links:
- docs/bpf: Document BPF_STRICT_BUILD=0 to tolerate test build failures
https://git.kernel.org/bpf/bpf-next/c/575d4e50192d
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-07-06 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 15:28 [PATCH] docs/bpf: Document BPF_STRICT_BUILD=0 to tolerate test build failures Ricardo B. Marlière
2026-07-06 18:38 ` Emil Tsalapatis
2026-07-06 22:30 ` 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=178337701189.1232545.1878877150316891466.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?UmljYXJkbyBCLiBNYXJsacOocmUgPHJibUBzdXNlLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=jolsa@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.