linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Usama Arif <usamaarif642@gmail.com>
To: acme@redhat.com
Cc: andrii@kernel.org, dcavalca@meta.com, chantr4@gmail.com,
	bpf@vger.kernel.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: New release for pahole
Date: Tue, 13 Aug 2024 15:54:17 +0100	[thread overview]
Message-ID: <0d978215-97d3-4b12-80ba-1fb29cd6ff52@gmail.com> (raw)

Hi,

Hope you are doing well. Just wanted to check when the next dwarves release would be? v1.27 broke clang compilation with the kernel [1], [2]. And v1.26 doesn't have the patch that is needed to build the kernel with memory allocation profiling. 

We can use the upstream dwarves for building the kernel, but it makes things trickier when trying to do it for production without a released package. If the next release is planned far off, would it be possible to do an intermediate one? something like v1.27.1.

Thanks

[1] https://gitlab.archlinux.org/archlinux/packaging/packages/pahole/-/issues/1
[2] https://issues.redhat.com/browse/RHEL-54022


                 reply	other threads:[~2024-08-13 14:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0d978215-97d3-4b12-80ba-1fb29cd6ff52@gmail.com \
    --to=usamaarif642@gmail.com \
    --cc=acme@redhat.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=chantr4@gmail.com \
    --cc=dcavalca@meta.com \
    --cc=linux-mm@kvack.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