From: Markus Elfring <Markus.Elfring@web.de>
To: Jie Zhan <zhanjie9@hisilicon.com>,
linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linuxarm@huawei.com, Beata Michalska <beata.michalska@arm.com>,
Bowen Yu <yubowen8@huawei.com>, Huisong Li <lihuisong@huawei.com>,
Ionela Voinescu <ionela.voinescu@arm.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Lifeng Zheng <zhenglifeng1@huawei.com>,
Prashant Malani <pmalani@google.com>
Subject: Re: [2/2] cpufreq: CPPC: Fix error handling in cppc_scale_freq_workfn()
Date: Thu, 31 Jul 2025 12:34:32 +0200 [thread overview]
Message-ID: <3773fcd3-6a76-499f-ae32-bb3cb8a62d8c@web.de> (raw)
In-Reply-To: <baef79be-5969-fa4b-3802-ac49d071b11b@hisilicon.com>
> We don't think it's necessarily a bugfix that should be backported to
> old/stable kernels. This is mainly an extra error handling for cases that
> may happen on our platform when a CPU is in a deep idle state.
I find mentioned tags relevant also according to proposed completion
of error handling.
Regards,
Markus
next prev parent reply other threads:[~2025-07-31 10:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 3:23 [PATCH 0/2] cpufreq: CPPC: Changing error message in CPPC FIE Bowen Yu
2025-07-30 3:23 ` [PATCH 1/2] cpufreq: CPPC: Don't warn on failing to read perf counters on offline cpus Bowen Yu
2025-07-30 3:23 ` [PATCH 2/2] cpufreq: CPPC: Fix error handling in cppc_scale_freq_workfn() Bowen Yu
2025-07-30 6:39 ` Viresh Kumar
2025-07-30 22:34 ` Prashant Malani
2025-07-31 8:32 ` Jie Zhan
2025-08-01 8:58 ` Prashant Malani
2025-08-04 6:21 ` Jie Zhan
2025-08-05 1:12 ` Prashant Malani
2025-08-05 4:58 ` Prashant Malani
2025-08-13 7:15 ` Jie Zhan
2025-08-13 9:30 ` Beata Michalska
2025-08-15 3:48 ` Jie Zhan
2025-07-30 18:38 ` Markus Elfring
2025-07-31 4:21 ` Jie Zhan
2025-07-31 10:34 ` Markus Elfring [this message]
2025-07-31 8:19 ` Beata Michalska
2025-07-31 8:52 ` Jie Zhan
2025-07-31 9:42 ` Beata Michalska
2025-08-04 6:31 ` Jie Zhan
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=3773fcd3-6a76-499f-ae32-bb3cb8a62d8c@web.de \
--to=markus.elfring@web.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=beata.michalska@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=lihuisong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=pmalani@google.com \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=yubowen8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.