From: Jonathan Corbet <corbet@lwn.net>
To: Mark Severson <gr3yf0x87@skyn3tlab.com>,
Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: changes.rst: set the pahole minimum back to 1.22
Date: Mon, 02 Nov 2026 09:21:08 -0700 [thread overview]
Message-ID: <87pkwncih7.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20261022014811.2803450-1-gr3yf0x87@skyn3tlab.com>
Mark Severson <gr3yf0x87@skyn3tlab.com> writes:
> Commit fd5425b67355 ("docs, resolve_btfids: Document kfunc BTF
> annotation emission") removed the paragraph saying that kfuncs annotated
> with KF_IMPLICIT_ARGS need pahole v1.26, because resolve_btfids now
> emits the kfunc BTF annotations that pahole used to produce. That
> paragraph was the reason the requirements table lists pahole 1.26, and
> the table was left unchanged. The text below the table and
> lib/Kconfig.debug (DEBUG_INFO_BTF depends on PAHOLE_VERSION >= 122)
> both still say 1.22.
>
> Set the table back to 1.22, in the English document and in the Italian
> translation, which carries the same table, and remove the Italian
> translation's copy of the paragraph that the English document no longer
> has.
>
> Checked by building linux-next 20261021 with pahole v1.25 and
> CONFIG_DEBUG_INFO_BTF=y: in the vmlinux BTF,
> bpf_task_work_schedule_signal has four arguments and the bpf_kfunc decl
> tag, and bpf_task_work_schedule_signal_impl keeps the
> struct bpf_prog_aux * argument, as Documentation/bpf/kfuncs.rst
> describes for KF_IMPLICIT_ARGS.
I've applied this patch, but removed that last paragraph, which doesn't
really belong in the permanent changelog.
> Fixes: fd5425b67355 ("docs, resolve_btfids: Document kfunc BTF annotation emission")
> Assisted-by: Claude
This line is no longer required, so I took it out as well.
> Signed-off-by: Mark Severson <gr3yf0x87@skyn3tlab.com>
Thanks,
jon
prev parent reply other threads:[~2026-11-02 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 1:34 [PATCH] " Mark Severson
2026-10-22 1:48 ` [PATCH v2] " Mark Severson
2026-10-24 10:09 ` Nguyen Duc Thinh
2026-10-25 13:22 ` Daniel Pereira
2026-10-25 20:20 ` Krzysztof Kozlowski
2026-11-02 16:21 ` Jonathan Corbet [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=87pkwncih7.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=federico.vaga@vaga.pv.it \
--cc=gr3yf0x87@skyn3tlab.com \
--cc=ihor.solodrai@linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.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
all inboxes | Powered by JetHome®