From: Christian Loehle <christian.loehle@arm.com>
To: rafael@kernel.org
Cc: zhenglifeng1@huawei.com, zhongqiu.han@oss.qualcomm.com,
viresh.kumar@linaro.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Mario Limonciello <mario.limonciello@amd.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Huang Rui <ray.huang@amd.com>, Perry Yuan <perry.yuan@amd.com>,
Vanshidhar Konda <vanshikonda@os.amperecomputing.com>,
Shubhang Kaushik <sh@gentwo.org>,
Pierre Gondois <pierre.gondois@arm.com>,
Beata Michalska <beata.michalska@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ionela Voinescu <ionela.voinescu@arm.com>,
Sudeep Holla <sudeep.holla@kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>,
Jeremy Linton <jeremy.linton@arm.com>,
jonathanh@nvidia.com, zhanjie9@hisilicon.com,
Christian Loehle <christian.loehle@arm.com>
Subject: [PATCH 0/2] MAINTAINERS: Update CPPC responsibilities
Date: Thu, 8 Oct 2026 22:28:30 +0100 [thread overview]
Message-ID: <20261008212832.354382-1-christian.loehle@arm.com> (raw)
Hi Rafael,
This series replaces Pierre with me as a reviewer for cppc_cpufreq and
adds a dedicated ACPI CPPC entry with you and me as maintainers.
The separate entry should help direct CPPC changes to people familiar
with its performance control semantics, register access mechanisms and
the platforms implementing it.
Thanks to Pierre for his work on CPPC.
Thanks,
Christian
Christian Loehle (2):
MAINTAINERS: cpufreq: Replace CPPC reviewer
MAINTAINERS: ACPI: Add a separate CPPC entry
MAINTAINERS | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
next reply other threads:[~2026-10-08 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 21:28 Christian Loehle [this message]
2026-10-08 21:28 ` [PATCH 1/2] MAINTAINERS: cpufreq: Replace CPPC reviewer Christian Loehle
2026-10-09 6:45 ` Pierre Gondois
2026-10-08 21:28 ` [PATCH 2/2] MAINTAINERS: ACPI: Add a separate CPPC entry Christian Loehle
2026-10-09 9:47 ` Sudeep Holla
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=20261008212832.354382-1-christian.loehle@arm.com \
--to=christian.loehle@arm.com \
--cc=beata.michalska@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=jeremy.linton@arm.com \
--cc=jonathanh@nvidia.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mario.limonciello@amd.com \
--cc=perry.yuan@amd.com \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=sh@gentwo.org \
--cc=sudeep.holla@kernel.org \
--cc=vanshikonda@os.amperecomputing.com \
--cc=viresh.kumar@linaro.org \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.com \
--cc=zhongqiu.han@oss.qualcomm.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