From: Sumit Gupta <sumitg@nvidia.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>
Cc: <linux-pm@vger.kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
kernel test robot <lkp@intel.com>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Sumit Gupta <sumitg@nvidia.com>
Subject: Re: [PATCH] cpufreq: tegra194: Staticize struct tegra_cpufreq_soc instances
Date: Mon, 18 Jul 2022 11:05:06 +0530 [thread overview]
Message-ID: <f4dc33b6-4023-1ac3-9365-c51175375bc7@nvidia.com> (raw)
In-Reply-To: <5c1a9b405d96848f2dac9aefcef121ad178872f4.1658109927.git.viresh.kumar@linaro.org>
On 18/07/22 07:35, Viresh Kumar wrote:
> External email: Use caution opening links or attachments
>
>
> Fix sparse warnings by marking these structures static.
>
> Fixes: 273bc890a2a8 ("cpufreq: tegra194: Add support for Tegra234")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Sumit Gupta <sumitg@nvidia.com>
> ---
> drivers/cpufreq/tegra194-cpufreq.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/tegra194-cpufreq.c b/drivers/cpufreq/tegra194-cpufreq.c
> index 2a6a98764a8c..1216046cf4c2 100644
> --- a/drivers/cpufreq/tegra194-cpufreq.c
> +++ b/drivers/cpufreq/tegra194-cpufreq.c
> @@ -162,7 +162,7 @@ static struct tegra_cpufreq_ops tegra234_cpufreq_ops = {
> .set_cpu_ndiv = tegra234_set_cpu_ndiv,
> };
>
> -const struct tegra_cpufreq_soc tegra234_cpufreq_soc = {
> +static const struct tegra_cpufreq_soc tegra234_cpufreq_soc = {
> .ops = &tegra234_cpufreq_ops,
> .actmon_cntr_base = 0x9000,
> .maxcpus_per_cluster = 4,
> @@ -430,7 +430,7 @@ static struct tegra_cpufreq_ops tegra194_cpufreq_ops = {
> .set_cpu_ndiv = tegra194_set_cpu_ndiv,
> };
>
> -const struct tegra_cpufreq_soc tegra194_cpufreq_soc = {
> +static const struct tegra_cpufreq_soc tegra194_cpufreq_soc = {
> .ops = &tegra194_cpufreq_ops,
> .maxcpus_per_cluster = 2,
> };
> --
> 2.31.1.272.g89b43f80a514
>
prev parent reply other threads:[~2022-07-18 5:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 2:05 Viresh Kumar
2022-07-18 5:35 ` Sumit Gupta [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=f4dc33b6-4023-1ac3-9365-c51175375bc7@nvidia.com \
--to=sumitg@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rafael@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®