From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: dwarves@vger.kernel.org
Cc: Jiri Olsa <jolsa@kernel.org>, Daniel Xu <dxu@dxuuu.xyz>,
Eduard Zingerman <eddyz87@gmail.com>,
Alan Maguire <alan.maguire@oracle.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Matthias Schwarzott <zzam@gentoo.org>
Subject: RFT: Prepping up pahole 1.27
Date: Thu, 6 Jun 2024 17:10:46 -0300 [thread overview]
Message-ID: <ZmIXxgbfIJGWmXer@x1> (raw)
Hi,
I just pushed what will be in v1.27 to the 'next' branch at:
https://git.kernel.org/pub/scm/devel/pahole/pahole.git next
The changes file for what will be in this release, mostly
reproducible builds and tags for kfuncs:
https://git.kernel.org/pub/scm/devel/pahole/pahole.git/tree/changes-v1.27?h=next
I plan to move it to 'master' and release it later today, so if
anyone could please do some more testing on it, that would be awesome,
Thanks!
- Arnaldo
next reply other threads:[~2024-06-06 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 20:10 Arnaldo Carvalho de Melo [this message]
2024-06-08 20:37 ` RFT: Prepping up pahole 1.27 Daniel Xu
2024-06-09 9:10 ` Alan Maguire
2024-06-09 15:39 ` Jiri Olsa
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=ZmIXxgbfIJGWmXer@x1 \
--to=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii.nakryiko@gmail.com \
--cc=dwarves@vger.kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=eddyz87@gmail.com \
--cc=jolsa@kernel.org \
--cc=zzam@gentoo.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