BPF List
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mark Severson" <gr3yf0x87@skyn3tlab.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH] docs: changes.rst: set the pahole minimum back to 1.22
Date: Thu, 22 Oct 2026 01:42:36 +0000	[thread overview]
Message-ID: <sashiko-outbox-180846@kernel.org> (raw)
In-Reply-To: <20261022013432.2638010-1-gr3yf0x87@skyn3tlab.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] docs: it_IT/process/changes.rst retains obsolete pahole 1.26 paragraph
--

commit d0caeb7c4f6cd56144ad9f71152e69d2bd461aa0
Author: Mark Severson <gr3yf0x87@skyn3tlab.com>

docs: changes.rst: set the pahole minimum back to 1.22

This commit lowers the minimum required pahole version in the requirements
table of Documentation/process/changes.rst and its Italian translation from
1.26 back to 1.22, following commit fd5425b67355 ("docs, resolve_btfids:
Document kfunc BTF annotation emission").

[ ... ]

> diff --git a/Documentation/translations/it_IT/process/changes.rst b/Documentation/translations/it_IT/process/changes.rst
> index 0be1292a87fc8..5adeee24cc713 100644
> --- a/Documentation/translations/it_IT/process/changes.rst
> +++ b/Documentation/translations/it_IT/process/changes.rst
> @@ -57,7 +57,7 @@ mcelog                 0.6              mcelog --version
>  mkimage (opzionale)    2017.01          mkimage --version
>  nfs-utils              1.0.5            showmount --version
>  openssl & libcrypto    1.0.0            openssl version
> -pahole                 1.26             pahole --version
> +pahole                 1.22             pahole --version
>  pcmciautils            004              pccardctl -V
>  PPP                    2.4.0            pppd --version
>  procps                 3.2.0            ps --version

[Severity: Low]
Commit fd5425b67355 ("docs, resolve_btfids: Document kfunc BTF annotation
emission") removed the KF_IMPLICIT_ARGS paragraph from the English
Documentation/process/changes.rst, but left the corresponding translated
paragraph in the pahole section below the Requisiti minimi correnti table in
Documentation/translations/it_IT/process/changes.rst:

pahole
------
...
Dalla versione 7.0, le kfunc annotate con KF_IMPLICIT_ARGS richiedono pahole
v1.26 o successivo. Senza questa versione, tali kfunc avranno prototipi BTF
errati in vmlinux, causando il fallimento del caricamento dei programmi BPF con
l'errore "func_proto incompatible with vmlinux". Molte kfunc in sched_ext sono
interessate da questo problema.

With the Requisiti minimi correnti table updated back to 1.22 here, should
that paragraph in the pahole section of
Documentation/translations/it_IT/process/changes.rst also be removed so the
table and the text below it do not contradict each other?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261022013432.2638010-1-gr3yf0x87@skyn3tlab.com?part=1

  reply	other threads:[~2026-10-22  1:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22  1:34 [PATCH] docs: changes.rst: set the pahole minimum back to 1.22 Mark Severson
2026-10-22  1:42 ` sashiko-bot [this message]
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

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=sashiko-outbox-180846@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=gr3yf0x87@skyn3tlab.com \
    --cc=sashiko-reviews@lists.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