Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
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,
	martin.lau@linux.dev, eddyz87@gmail.com, memxor@gmail.com,
	song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
	shuah@kernel.org, nathan@kernel.org,
	nick.desaulniers+lkml@gmail.com, morbo@google.com,
	justinstitt@google.com, bpf@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev, alan.maguire@oracle.com
Subject: Re: [PATCH bpf-next RESEND v12 00/11] selftests/bpf: Tolerate partial builds across kernel configs
Date: Fri, 05 Jun 2026 21:30:27 +0000	[thread overview]
Message-ID: <178069502789.3925764.15952069390143619686.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260602-selftests-bpf_misconfig-v12-0-27f898b3ba26@suse.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue, 02 Jun 2026 10:02:49 -0300 you wrote:
> Currently the BPF selftests can only be built by using the minimum kernel
> configuration defined in tools/testing/selftests/bpf/config*. This poses a
> problem in distribution kernels that may have some of the flags disabled or
> set as module. For example, we have been running the tests regularly in
> openSUSE Tumbleweed [1] [2] but to work around this fact we created a
> special package [3] that build the tests against an auxiliary vmlinux with
> the BPF Kconfig. We keep a list of known issues that may happen due to,
> amongst other things, configuration mismatches [4] [5].
> 
> [...]

Here is the summary with links:
  - [bpf-next,RESEND,v12,01/11] selftests/bpf: Add BPF_STRICT_BUILD toggle
    https://git.kernel.org/bpf/bpf-next/c/a6850fa388f6
  - [bpf-next,RESEND,v12,02/11] selftests/bpf: Fix test_kmods KDIR to honor O= and distro kernels
    https://git.kernel.org/bpf/bpf-next/c/9779193e871b
  - [bpf-next,RESEND,v12,03/11] selftests/bpf: Tolerate BPF and skeleton generation failures
    https://git.kernel.org/bpf/bpf-next/c/c476bdf27657
  - [bpf-next,RESEND,v12,04/11] selftests/bpf: Avoid rebuilds when running emit_tests
    https://git.kernel.org/bpf/bpf-next/c/a97bfc9aae07
  - [bpf-next,RESEND,v12,05/11] selftests/bpf: Make skeleton headers order-only prerequisites of .test.d
    https://git.kernel.org/bpf/bpf-next/c/5498e47741c8
  - [bpf-next,RESEND,v12,06/11] selftests/bpf: Tolerate test file compilation failures
    https://git.kernel.org/bpf/bpf-next/c/9c4de137a9a5
  - [bpf-next,RESEND,v12,07/11] selftests/bpf: Skip tests whose objects were not built
    https://git.kernel.org/bpf/bpf-next/c/aeb73a9f301d
  - [bpf-next,RESEND,v12,08/11] selftests/bpf: Allow test_progs to link with a partial object set
    https://git.kernel.org/bpf/bpf-next/c/af490669fd33
  - [bpf-next,RESEND,v12,09/11] selftests/bpf: Tolerate benchmark build failures
    https://git.kernel.org/bpf/bpf-next/c/f813a4d6877e
  - [bpf-next,RESEND,v12,10/11] selftests/bpf: Provide weak definitions for cross-test functions
    https://git.kernel.org/bpf/bpf-next/c/b85e63cb65f9
  - [bpf-next,RESEND,v12,11/11] selftests/bpf: Tolerate missing files during install
    https://git.kernel.org/bpf/bpf-next/c/3ca6543464f8

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-06-05 21:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 13:02 [PATCH bpf-next RESEND v12 00/11] selftests/bpf: Tolerate partial builds across kernel configs Ricardo B. Marlière
2026-06-02 13:02 ` [PATCH bpf-next RESEND v12 01/11] selftests/bpf: Add BPF_STRICT_BUILD toggle Ricardo B. Marlière
2026-06-02 13:02 ` [PATCH bpf-next RESEND v12 02/11] selftests/bpf: Fix test_kmods KDIR to honor O= and distro kernels Ricardo B. Marlière
2026-06-02 13:37   ` bot+bpf-ci
2026-06-02 13:02 ` [PATCH bpf-next RESEND v12 03/11] selftests/bpf: Tolerate BPF and skeleton generation failures Ricardo B. Marlière
2026-06-02 13:02 ` [PATCH bpf-next RESEND v12 04/11] selftests/bpf: Avoid rebuilds when running emit_tests Ricardo B. Marlière
2026-06-02 13:02 ` [PATCH bpf-next RESEND v12 05/11] selftests/bpf: Make skeleton headers order-only prerequisites of .test.d Ricardo B. Marlière
2026-06-02 13:37   ` bot+bpf-ci
2026-06-02 13:02 ` [PATCH bpf-next RESEND v12 06/11] selftests/bpf: Tolerate test file compilation failures Ricardo B. Marlière
2026-06-02 13:02 ` [PATCH bpf-next RESEND v12 07/11] selftests/bpf: Skip tests whose objects were not built Ricardo B. Marlière
2026-06-02 13:02 ` [PATCH bpf-next RESEND v12 08/11] selftests/bpf: Allow test_progs to link with a partial object set Ricardo B. Marlière
2026-06-02 13:02 ` [PATCH bpf-next RESEND v12 09/11] selftests/bpf: Tolerate benchmark build failures Ricardo B. Marlière
2026-06-02 13:02 ` [PATCH bpf-next RESEND v12 10/11] selftests/bpf: Provide weak definitions for cross-test functions Ricardo B. Marlière
2026-06-02 13:03 ` [PATCH bpf-next RESEND v12 11/11] selftests/bpf: Tolerate missing files during install Ricardo B. Marlière
2026-06-02 13:34 ` [PATCH bpf-next RESEND v12 00/11] selftests/bpf: Tolerate partial builds across kernel configs Ricardo B. Marlière
2026-06-05 21: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=178069502789.3925764.15952069390143619686.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=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --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