From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: bot+bpf-ci@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, akpm@linux-foundation.org,
nathan@kernel.org, nsc@kernel.org, tj@kernel.org,
void@manifault.com, arighi@nvidia.com, changwoo@igalia.com,
shuah@kernel.org, nick.desaulniers+lkml@gmail.com,
morbo@google.com, justinstitt@google.com,
alan.maguire@oracle.com, dolinux.peng@gmail.com
Cc: bpf@vger.kernel.org, dwarves@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
martin.lau@kernel.org, clm@meta.com
Subject: Re: [PATCH bpf-next v3 4/6] lib/Kconfig.debug: Set the minimum required pahole version to v1.22
Date: Fri, 5 Dec 2025 14:51:22 -0800 [thread overview]
Message-ID: <45232d20-22f0-47e2-aada-8aaaa6106af0@linux.dev> (raw)
In-Reply-To: <2475b1c6ce4e9249129ca007de68b80cc4d32a0949e391a2de4467bf599f25f7@mail.kernel.org>
On 12/5/25 2:49 PM, bot+bpf-ci@kernel.org wrote:
>> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
>> index 742b23ef0d8b..3abf3ae554b6 100644
>> --- a/lib/Kconfig.debug
>> +++ b/lib/Kconfig.debug
>
> [ ... ]
>
>> -config PAHOLE_HAS_SPLIT_BTF
>> - def_bool PAHOLE_VERSION >= 119
>
> The PAHOLE_HAS_SPLIT_BTF config option was removed here.
>
> [ ... ]
>
>> diff --git a/tools/sched_ext/README.md b/tools/sched_ext/README.md
>> index 16a42e4060f6..56a9d1557ac4 100644
>> --- a/tools/sched_ext/README.md
>> +++ b/tools/sched_ext/README.md
>> @@ -65,7 +65,6 @@ It's also recommended that you also include the following Kconfig options:
>> ```
>> CONFIG_BPF_JIT_ALWAYS_ON=y
>> CONFIG_BPF_JIT_DEFAULT_ON=y
>> -CONFIG_PAHOLE_HAS_SPLIT_BTF=y
>> CONFIG_PAHOLE_HAS_BTF_TAG=y
>> ```
>
> The PAHOLE_HAS_SPLIT_BTF reference was removed from
> tools/sched_ext/README.md, but Documentation/scheduler/sched-ext.rst
> still contains this config option at line 46. Should that documentation
> file also be updated to remove this obsolete config option?
Yes. I thought I removed it, but the change got lost in translation.
>
>
> ---
> AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
> See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
>
> CI run summary: https://github.com/kernel-patches/bpf/actions/runs/19978081551
next prev parent reply other threads:[~2025-12-05 22:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 22:30 [PATCH bpf-next v3 0/6] resolve_btfids: Support for BTF modifications Ihor Solodrai
2025-12-05 22:30 ` [PATCH bpf-next v3 1/6] resolve_btfids: Rename object btf field to btf_path Ihor Solodrai
2025-12-12 7:10 ` Eduard Zingerman
2025-12-05 22:30 ` [PATCH bpf-next v3 2/6] resolve_btfids: Factor out load_btf() Ihor Solodrai
2025-12-05 22:57 ` bot+bpf-ci
2025-12-05 23:12 ` Ihor Solodrai
2025-12-05 23:18 ` Chris Mason
2025-12-12 7:10 ` Eduard Zingerman
2025-12-05 22:30 ` [PATCH bpf-next v3 3/6] resolve_btfids: Introduce enum btf_id_kind Ihor Solodrai
2025-12-12 7:09 ` Eduard Zingerman
2025-12-16 2:31 ` Ihor Solodrai
2025-12-16 2:38 ` Eduard Zingerman
2025-12-16 2:52 ` Ihor Solodrai
2025-12-16 2:54 ` Eduard Zingerman
2025-12-05 22:30 ` [PATCH bpf-next v3 4/6] lib/Kconfig.debug: Set the minimum required pahole version to v1.22 Ihor Solodrai
2025-12-05 22:49 ` bot+bpf-ci
2025-12-05 22:51 ` Ihor Solodrai [this message]
2025-12-06 0:32 ` Andrii Nakryiko
2025-12-06 0:58 ` Ihor Solodrai
2025-12-12 7:09 ` Eduard Zingerman
2025-12-12 17:26 ` Alan Maguire
2025-12-16 2:40 ` Ihor Solodrai
2025-12-05 22:30 ` [PATCH bpf-next v3 5/6] selftests/bpf: Run resolve_btfids only for relevant .test.o objects Ihor Solodrai
2025-12-05 22:35 ` [PATCH bpf-next v3 6/6] resolve_btfids: change in-place update with raw binary output Ihor Solodrai
2025-12-06 1:13 ` Andrii Nakryiko
2025-12-06 1:37 ` Ihor Solodrai
2025-12-12 7:08 ` Eduard Zingerman
2025-12-16 2:16 ` Ihor Solodrai
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=45232d20-22f0-47e2-aada-8aaaa6106af0@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=arighi@nvidia.com \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=dolinux.peng@gmail.com \
--cc=dwarves@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=kpsingh@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nsc@kernel.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.com \
--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.