From: Wang Yugui <wangyugui@e16-tech.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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
Date: Sun, 24 May 2026 08:56:41 +0800 [thread overview]
Message-ID: <20260524085640.88D0.409509F4@e16-tech.com> (raw)
In-Reply-To: <2026052319-chastity-viper-7530@gregkh>
Hi,
> I'm announcing the release of the 6.12.91 kernel.
>
> All users of the 6.12 kernel series must upgrade.
>
> The updated 6.12.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.12.y
> and can be browsed at the normal kernel.org git web browser:
> https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
2 regression of 6.12.91 are found here. Both of them are in perf tool
1, undefined reference to `parse_events__term_type_str'
Could we add a patch
d2f3ecb0ca2099d13bf8bf69219214c1425dc453 perf parse-events: Expose/rename config_term_name
or do some funcation rename(parse_events__term_type_str->config_term_name)?
2, undefined first_wildcard_match
Could we revert the patch (perf cgroup: Update metric leader in evlist__expand_cgroup)?
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2026/05/24
next prev parent reply other threads:[~2026-05-24 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 11:46 Greg Kroah-Hartman
2026-05-23 11:46 ` Greg Kroah-Hartman
2026-05-24 0:56 ` Wang Yugui [this message]
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
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=20260524085640.88D0.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®