From: Sam James <sam@gentoo.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: dwarves@vger.kernel.org, da.gomez@samsung.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-modules@vger.kernel.org, masahiroy@kernel.org,
mcgrof@kernel.org, paolo.pisati@canonical.com,
petr.pavlu@suse.com, samitolvanen@google.com,
Matthias Schwarzott <zzam@gentoo.org>
Subject: Re: [PATCH] kbuild: Require pahole >v1.29 with GENDWARFKSYMS and BTF on X86
Date: Tue, 08 Apr 2025 04:04:26 +0100 [thread overview]
Message-ID: <87semj4amd.fsf@gentoo.org> (raw)
In-Reply-To: <7b0bd9be-c3ef-40d4-9465-92f3e69a07d1@oracle.com>
Alan Maguire <alan.maguire@oracle.com> writes:
> On 07/04/2025 09:25, Sam James wrote:
>> [with regard to
>> https://lore.kernel.org/linux-kbuild/20250320232757.2283956-2-samitolvanen@google.com/]
>>
>> Would it be possible to have a new release with that fix, to avoid
>> distros all having to cherrypick the fix commit?
>>
>> Thanks in advance,
>> sam
>>
>
> We're planning to release 1.30 shortly to follow the recent 6.14 kernel
> release - hopefully this week, or perhaps early next week if any bugs
> are discovered during final testing.
>
> If folks can help by testing the next branch of
>
> https://git.kernel.org/pub/scm/devel/pahole/pahole.git
>
> ...prior to that, that would be great. Thanks!
Will do, thanks!
>
> Alan
prev parent reply other threads:[~2025-04-08 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250320232757.2283956-2-samitolvanen@google.com>
2025-04-07 8:25 ` [PATCH] kbuild: Require pahole >v1.29 with GENDWARFKSYMS and BTF on X86 Sam James
2025-04-07 12:50 ` Alan Maguire
2025-04-08 3:04 ` Sam James [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=87semj4amd.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=alan.maguire@oracle.com \
--cc=da.gomez@samsung.com \
--cc=dwarves@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=paolo.pisati@canonical.com \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--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