From: Markus Elfring <Markus.Elfring@web.de>
To: Gaowei Pu <pugaowei@oppo.com>, linux-pm@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH v2] cpufreq: queue policy->update work to a dedicated thread
Date: Thu, 17 Jul 2025 18:25:14 +0200 [thread overview]
Message-ID: <5bf8c7da-19bb-4286-9f02-369e09ffac5e@web.de> (raw)
In-Reply-To: <20250717085110.1468-1-pugaowei@oppo.com>
> when we add a dedicated highpri workqueue to do the policy update work.
high-priority?
> Therefore, we keep the thread and will add a vendor hook in andorid aosp
Android OSP?
> branch lately so we can customize the thread conveniently.
>
> Changes in v2:
…
Please move your patch version descriptions behind a marker line.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16-rc6#n784
Regards,
Markus
next prev parent reply other threads:[~2025-07-17 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 8:51 [PATCH v2] cpufreq: queue policy->update work to a dedicated thread Gaowei Pu
2025-07-17 16:25 ` Markus Elfring [this message]
2025-07-17 18:13 ` Rafael J. Wysocki
2025-07-18 7:32 ` Gaowei Pu
2025-07-18 1:57 ` kernel test robot
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=5bf8c7da-19bb-4286-9f02-369e09ffac5e@web.de \
--to=markus.elfring@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pugaowei@oppo.com \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
/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