Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Gondois <pierre.gondois@arm.com>
To: Christian Loehle <christian.loehle@arm.com>, 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>,
	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
Subject: Re: [PATCH 1/2] MAINTAINERS: cpufreq: Replace CPPC reviewer
Date: Fri, 9 Oct 2026 08:45:47 +0200	[thread overview]
Message-ID: <dc46b576-fa33-4475-b69b-70bd8cb53f1c@arm.com> (raw)
In-Reply-To: <20261008212832.354382-2-christian.loehle@arm.com>

Hi Christian,

Thanks a lot for this,

Reviewed-by: Pierre Gondois <pierre.gondois@arm.com>

On 10/8/26 23:28, Christian Loehle wrote:
> Take over CPPC cpufreq review duties from Pierre Gondois. Thanks to
> Pierre for his reviews and contributions to the driver.
>
> Signed-off-by: Christian Loehle <christian.loehle@arm.com>
> ---
>   MAINTAINERS | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 65e8a4b5c90b..3064942ef05c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6765,7 +6765,7 @@ M:	"Rafael J. Wysocki" <rafael@kernel.org>
>   M:	Viresh Kumar <viresh.kumar@linaro.org>
>   R:	Jie Zhan <zhanjie9@hisilicon.com>
>   R:	Lifeng Zheng <zhenglifeng1@huawei.com>
> -R:	Pierre Gondois <pierre.gondois@arm.com>
> +R:	Christian Loehle <christian.loehle@arm.com>
>   R:	Sumit Gupta <sumitg@nvidia.com>
>   L:	linux-pm@vger.kernel.org
>   S:	Maintained


  reply	other threads:[~2026-10-09  6:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 21:28 [PATCH 0/2] MAINTAINERS: Update CPPC responsibilities Christian Loehle
2026-10-08 21:28 ` [PATCH 1/2] MAINTAINERS: cpufreq: Replace CPPC reviewer Christian Loehle
2026-10-09  6:45   ` Pierre Gondois [this message]
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=dc46b576-fa33-4475-b69b-70bd8cb53f1c@arm.com \
    --to=pierre.gondois@arm.com \
    --cc=beata.michalska@arm.com \
    --cc=christian.loehle@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=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