From: Catalin Marinas <catalin.marinas@arm.com>
To: will@kernel.org, rafael@kernel.org, viresh.kumar@linaro.org,
sudeep.holla@arm.com, gregkh@linuxfoundation.org,
dakr@kernel.org, beata.michalska@arm.com,
ionela.voinescu@arm.com, Lifeng Zheng <zhenglifeng1@huawei.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linuxarm@huawei.com, jonathan.cameron@huawei.com,
vincent.guittot@linaro.org, zhanjie9@hisilicon.com,
lihuisong@huawei.com, yubowen8@huawei.com,
zhangpengjie2@huawei.com, wangzhi12@huawei.com,
linhongye@h-partners.com
Subject: Re: [PATCH v6 0/3] arm64: topology: Handle AMU FIE setup on CPU hotplug
Date: Fri, 28 Nov 2025 15:49:17 +0000 [thread overview]
Message-ID: <aSnEfTJ3WRx6iJU5@arm.com> (raw)
In-Reply-To: <176409538230.296584.10511015168201991664.b4-ty@arm.com>
On Tue, Nov 25, 2025 at 06:29:53PM +0000, Catalin Marinas wrote:
> On Wed, 19 Nov 2025 16:13:53 +0800, Lifeng Zheng wrote:
> > Solve a problem that causes CPUs Setup AMU FIE failed in a corner case,
> > even though they're eligible.
> >
> > Changelog:
> >
> > v6:
> >
> > [...]
>
> Applied to arm64 (for-next/topology), thanks!
>
> [1/3] arm64: topology: Skip already covered CPUs when setting freq source
> https://git.kernel.org/arm64/c/a04fd8bcd6aa
> [2/3] cpufreq: Add new helper function returning cpufreq policy
> https://git.kernel.org/arm64/c/709a16bebc54
> [3/3] arm64: topology: Handle AMU FIE setup on CPU hotplug
> https://git.kernel.org/arm64/c/1ea7e37e26b3
I think Beata still has to review the last patch in the series, so I'll
drop it for now from -next. Sorry about this.
--
Catalin
next prev parent reply other threads:[~2025-11-28 15:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 8:13 [PATCH v6 0/3] arm64: topology: Handle AMU FIE setup on CPU hotplug Lifeng Zheng
2025-11-19 8:13 ` [PATCH v6 1/3] arm64: topology: Skip already covered CPUs when setting freq source Lifeng Zheng
2025-11-19 8:13 ` [PATCH v6 2/3] cpufreq: Add new helper function returning cpufreq policy Lifeng Zheng
2025-11-19 8:13 ` [PATCH v6 3/3] arm64: topology: Handle AMU FIE setup on CPU hotplug Lifeng Zheng
2025-11-25 18:29 ` [PATCH v6 0/3] " Catalin Marinas
2025-11-28 15:49 ` Catalin Marinas [this message]
2025-12-01 15:27 ` Beata Michalska
2025-12-02 3:05 ` zhenglifeng (A)
2025-12-02 3:08 ` zhenglifeng (A)
2025-12-02 15:31 ` Beata Michalska
2025-12-03 9:44 ` zhenglifeng (A)
2025-12-12 9:27 ` zhenglifeng (A)
2025-12-12 20:08 ` Will Deacon
2025-12-20 9:09 ` zhenglifeng (A)
2025-12-29 22:12 ` Beata Michalska
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=aSnEfTJ3WRx6iJU5@arm.com \
--to=catalin.marinas@arm.com \
--cc=beata.michalska@arm.com \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ionela.voinescu@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=lihuisong@huawei.com \
--cc=linhongye@h-partners.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=wangzhi12@huawei.com \
--cc=will@kernel.org \
--cc=yubowen8@huawei.com \
--cc=zhangpengjie2@huawei.com \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.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).