From: Mario Limonciello <mario.limonciello@amd.com>
To: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>,
gautham.shenoy@amd.com, perry.yuan@amd.com, rafael@kernel.org,
viresh.kumar@linaro.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] cpufreq/amd-pstate: Refactor amd_pstate_init()
Date: Thu, 17 Oct 2024 13:06:27 -0500 [thread overview]
Message-ID: <2bfa4179-3d45-44b1-9d51-a4317a548cf1@amd.com> (raw)
In-Reply-To: <20241017100528.300143-1-Dhananjay.Ugwekar@amd.com>
On 10/17/2024 05:05, Dhananjay Ugwekar wrote:
> Replace code chunks with function calls, improve readability and
> reduce redundancy.
>
> Base: superm1/linux-next + https://lore.kernel.org/linux-pm/20241017053927.25285-1-Dhananjay.Ugwekar@amd.com/
>
> Dhananjay Ugwekar (4):
> cpufreq/amd-pstate: Call amd_pstate_register() in amd_pstate_init()
> cpufreq/amd-pstate: Call amd_pstate_set_driver() in
> amd_pstate_register_driver()
> cpufreq/amd-pstate: Remove the switch case in amd_pstate_init()
> cpufreq/amd-pstate: Remove the redundant amd_pstate_set_driver() call
>
> drivers/cpufreq/amd-pstate.c | 79 +++++++++++++-----------------------
> 1 file changed, 29 insertions(+), 50 deletions(-)
>
Thanks for the improvement.
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
prev parent reply other threads:[~2024-10-17 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 10:05 [PATCH 0/4] cpufreq/amd-pstate: Refactor amd_pstate_init() Dhananjay Ugwekar
2024-10-17 10:05 ` [PATCH 1/4] cpufreq/amd-pstate: Call amd_pstate_register() in amd_pstate_init() Dhananjay Ugwekar
2024-10-17 10:05 ` [PATCH 2/4] cpufreq/amd-pstate: Call amd_pstate_set_driver() in amd_pstate_register_driver() Dhananjay Ugwekar
2024-10-17 10:05 ` [PATCH 3/4] cpufreq/amd-pstate: Remove the switch case in amd_pstate_init() Dhananjay Ugwekar
2024-10-17 10:05 ` [PATCH 4/4] cpufreq/amd-pstate: Remove the redundant amd_pstate_set_driver() call Dhananjay Ugwekar
2024-10-26 11:58 ` Klara Modin
2024-10-27 4:27 ` Mario Limonciello
2024-10-27 11:41 ` Klara Modin
2024-10-17 18:06 ` Mario Limonciello [this message]
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=2bfa4179-3d45-44b1-9d51-a4317a548cf1@amd.com \
--to=mario.limonciello@amd.com \
--cc=Dhananjay.Ugwekar@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=perry.yuan@amd.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