From: Wang Yugui <wangyugui@e16-tech.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 6.12.91 - perf build break: undefined parse_events__term_type_str / first_wildcard_match
Date: Fri, 29 May 2026 13:18:46 +0800 [thread overview]
Message-ID: <20260529131845.70D6.409509F4@e16-tech.com> (raw)
In-Reply-To: <20260527-agent5-item001-perf@kernel.org>
Hi,
> > > 1, undefined reference to parse_events__term_type_str.
> > > Could we backport "perf parse-events: Expose/rename
> > > config_term_name" (d2f3ecb0ca20)?
>
> Queued d2f3ecb0ca20 for 6.12.y, thanks.
>
> > > 2, undefined first_wildcard_match.
> > > Could we revert the patch (perf cgroup: Update metric leader in
> > > evlist__expand_cgroup)?
>
> Still looking into this one - could you share the failing build log
> (and the .config) so we can confirm the right fix?
>
with the flowing 4 patches of queue-6.12 on the 6.12.91, the kernel packages
are build without any errror.
revert-perf-cgroup-update-metric-leader-in-evlist__e.patch
revert-perf-python-add-parse_events-function.patch
revert-perf-tool_pmu-fix-aggregation-on-duration_tim.patch
revert-perf-tool_pmu-factor-tool-events-into-their-o.patch
Sorry to reply to this too later.
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2026/05/29
prev parent reply other threads:[~2026-05-29 5:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 11:46 Linux 6.12.91 Greg Kroah-Hartman
2026-05-23 11:46 ` Greg Kroah-Hartman
2026-05-24 0:56 ` Wang Yugui
2026-05-26 11:35 ` Sasha Levin
2026-05-27 19:48 ` Linux 6.12.91 - perf build break: undefined parse_events__term_type_str / first_wildcard_match Sasha Levin
2026-05-29 5:18 ` Wang Yugui [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=20260529131845.70D6.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.