public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hemanth Malla <vmalla@linux.microsoft.com>
To: ihor.solodrai@linux.dev
Cc: alan.maguire@oracle.com, andrii@kernel.org, ast@kernel.org,
	bpf@vger.kernel.org, corbet@lwn.net, daniel@iogearbox.net,
	dwarves@vger.kernel.org, eddyz87@gmail.com, haoluo@google.com,
	john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	martin.lau@linux.dev, sdf@fomichev.me, song@kernel.org,
	vmalla@linux.microsoft.com, vmalla@microsoft.com,
	yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next] bpf, docs: Update pahole to 1.28 for selftests
Date: Sat,  3 Jan 2026 21:55:22 -0800	[thread overview]
Message-ID: <1767506122-8122-1-git-send-email-vmalla@linux.microsoft.com> (raw)
In-Reply-To: <bcd23277-a18e-4bb5-ba76-3416c84511c2@linux.dev>

Hi Ihor,

> 1.28 is needed for --distilled_base [1], which is only a requirement
> for tests using modules. Many other tests are likely to work with
> older versions, but the minimum for the kernel build is 1.22 now [2].
> 
> Not sure if it's worth it to add this nuance to the QA doc, although
> in general we should recommend people running the selftests to use the
> latest pahole release. Maybe add a comment?

Thanks for the references. Makes sense to include these in the docs.
I'll send out a new patch.

Thanks,
Hemanth Malla


      parent reply	other threads:[~2026-01-04  5:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 11:13 [PATCH bpf-next] bpf, docs: Update pahole to 1.28 for selftests Hemanth Malla
2026-01-02 15:33 ` Ihor Solodrai
2026-01-03  9:11   ` Bagas Sanjaya
2026-01-05 21:46     ` Andrii Nakryiko
2026-01-07 13:19       ` Bagas Sanjaya
2026-01-04  5:55   ` Hemanth Malla [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=1767506122-8122-1-git-send-email-vmalla@linux.microsoft.com \
    --to=vmalla@linux.microsoft.com \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --cc=dwarves@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=vmalla@microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox