From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: James Clark <james.clark@linaro.org>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Ian Rogers <irogers@google.com>,
patches@lists.linux.dev, Namhyung Kim <namhyung@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Yang Jihong <yangjihong@bytedance.com>,
Dominique Martinet <asmadeus@codewreck.org>,
Colin Ian King <colin.i.king@gmail.com>,
Howard Chu <howardchu95@gmail.com>, Ze Gao <zegao2021@gmail.com>,
Yicong Yang <yangyicong@hisilicon.com>,
Weilin Wang <weilin.wang@intel.com>,
Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
Yang Li <yang.lee@linux.alibaba.com>, Leo Yan <leo.yan@linux.dev>,
ak@linux.intel.com, Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
linux-arm-kernel@lists.infradead.org,
Sun Haiyong <sunhaiyong@loongson.cn>,
John Garry <john.g.garry@oracle.com>,
Justin Forbes <jforbes@fedoraproject.org>
Subject: Re: [PATCH 6.12 470/826] perf stat: Uniquify event name improvements
Date: Thu, 5 Dec 2024 10:27:33 +0100 [thread overview]
Message-ID: <2024120517-reason-icing-8e77@gregkh> (raw)
In-Reply-To: <deb83bf5-2342-479c-b1bd-7f8c49f5b1d4@linaro.org>
On Thu, Dec 05, 2024 at 08:54:15AM +0000, James Clark wrote:
>
>
> On 03/12/2024 5:24 pm, Thorsten Leemhuis wrote:
> > On 03.12.24 15:43, Greg Kroah-Hartman wrote:
> > > 6.12-stable review patch. If anyone has any objections, please let me know.
> > >
> > > ------------------
> > >
> > > From: Ian Rogers <irogers@google.com>
> > >
> > > [ Upstream commit 057f8bfc6f7070577523d1e3081081bbf4229c1c ]
> > >
> > > Without aggregation on Intel:
> >
> > My 6.11.y-rc and 6.12.y-rc builds for Fedora failed when building perf.
> > I did not bisect, but from a brief look at the error message (see
> > below) I suspect it might be caused by this patch, which is the
> > second of the patch-set "Event parsing fixes":
> > https://lore.kernel.org/all/20240926144851.245903-1-james.clark@linaro.org/
> >
> > To my untrained eyes and from a quick look I guess the first patch
> > in the series needs to be backported as well:
> > perf evsel: Add alternate_hw_config and use in evsel__match
> > https://lore.kernel.org/all/20240926144851.245903-2-james.clark@linaro.org/
> >
> > This is 22a4db3c36034e ("perf evsel: Add alternate_hw_config
> > and use in evsel__match") in mainline. I tried to cherry-pick it
> > on-top of 6.12.2-rc1, but there were a few small conflicts.
> >
> > Ciao, Thorsten
> >
>
> Yes I imagine both commits are required. Another option is to not backport
> this one. It looks like it's mainly to fix a test, nothing is missing or
> wrong from the output, just the formatting is off.
Thanks, I'll just drop this patch from the stable queue for now.
greg k-h
prev parent reply other threads:[~2024-12-05 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241203144743.428732212@linuxfoundation.org>
2024-12-03 14:43 ` [PATCH 6.12 466/826] perf cs-etm: Dont flush when packet_queue fills up Greg Kroah-Hartman
2024-12-03 14:43 ` [PATCH 6.12 470/826] perf stat: Uniquify event name improvements Greg Kroah-Hartman
2024-12-03 17:24 ` Thorsten Leemhuis
2024-12-04 17:43 ` Thorsten Leemhuis
2024-12-05 8:54 ` James Clark
2024-12-05 9:27 ` Greg Kroah-Hartman [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=2024120517-reason-icing-8e77@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ak@linux.intel.com \
--cc=asmadeus@codewreck.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=colin.i.king@gmail.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jforbes@fedoraproject.org \
--cc=john.g.garry@oracle.com \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@leemhuis.info \
--cc=mike.leach@linaro.org \
--cc=namhyung@kernel.org \
--cc=patches@lists.linux.dev \
--cc=renyu.zj@linux.alibaba.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sunhaiyong@loongson.cn \
--cc=weilin.wang@intel.com \
--cc=will@kernel.org \
--cc=yang.lee@linux.alibaba.com \
--cc=yangjihong@bytedance.com \
--cc=yangyicong@hisilicon.com \
--cc=zegao2021@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).