From: Viresh Kumar <viresh.kumar@linaro.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Thierry Reding <thierry.reding@gmail.com>,
linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
Sumit Gupta <sumitg@nvidia.com>
Subject: Re: [PATCH 0/4] CPUFREQ clean-ups for Tegra186 and Tegra194
Date: Mon, 7 Dec 2020 13:03:01 +0530 [thread overview]
Message-ID: <20201207073301.nar5vbqpgxbdgs5u@vireshk-i7> (raw)
In-Reply-To: <20201202091419.307192-1-jonathanh@nvidia.com>
On 02-12-20, 09:14, Jon Hunter wrote:
> This series includes some clean-ups for the Tegra186 and Tegra194
> CPUFREQ drivers.
>
> Jon Hunter (4):
> cpufreq: tegra186: Fix sparse 'incorrect type in assignment' warning
> cpufreq: tegra186: Simplify cluster information lookup
> cpufreq: tegra194: Remove unnecessary frequency calculation
> cpufreq: tegra194: Rename tegra194_get_speed_common function
>
> drivers/cpufreq/tegra186-cpufreq.c | 122 +++++++++++++----------------
> drivers/cpufreq/tegra194-cpufreq.c | 12 +--
> 2 files changed, 57 insertions(+), 77 deletions(-)
Applied. Thanks.
--
viresh
prev parent reply other threads:[~2020-12-07 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 9:14 [PATCH 0/4] CPUFREQ clean-ups for Tegra186 and Tegra194 Jon Hunter
2020-12-02 9:14 ` [PATCH 1/4] cpufreq: tegra186: Fix sparse 'incorrect type in assignment' warning Jon Hunter
2020-12-02 9:14 ` [PATCH 2/4] cpufreq: tegra186: Simplify cluster information lookup Jon Hunter
2020-12-02 9:14 ` [PATCH 3/4] cpufreq: tegra194: Remove unnecessary frequency calculation Jon Hunter
2020-12-02 9:14 ` [PATCH 4/4] cpufreq: tegra194: Rename tegra194_get_speed_common function Jon Hunter
2020-12-07 7:33 ` Viresh Kumar [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=20201207073301.nar5vbqpgxbdgs5u@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sumitg@nvidia.com \
--cc=thierry.reding@gmail.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