From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Dirk Brandewie <dirk.j.brandewie@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: linux-next: Tree for May 25 (cpufreq/intel_pstate.c)
Date: Tue, 25 May 2021 11:23:33 -0700 [thread overview]
Message-ID: <4c20c8b0-145e-bfbf-003c-28c8eeac72dc@infradead.org> (raw)
In-Reply-To: <20210525163932.785c1a2a@canb.auug.org.au>
On 5/24/21 11:39 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210524:
>
on x86_64:
# CONFIG_ACPI is not set
../drivers/cpufreq/intel_pstate.c:495:59: warning: ‘struct cppc_perf_caps’ declared inside parameter list will not be visible outside of this definition or declaration
static bool intel_pstate_cppc_perf_valid(u32 perf, struct cppc_perf_caps *caps)
^~~~~~~~~~~~~~
../drivers/cpufreq/intel_pstate.c: In function ‘intel_pstate_cppc_perf_valid’:
../drivers/cpufreq/intel_pstate.c:497:29: error: dereferencing pointer to incomplete type ‘struct cppc_perf_caps’
return perf && perf <= caps->highest_perf && perf >= caps->lowest_perf;
^~
../drivers/cpufreq/intel_pstate.c: At top level:
../drivers/cpufreq/intel_pstate.c:501:13: warning: ‘struct cppc_perf_caps’ declared inside parameter list will not be visible outside of this definition or declaration
struct cppc_perf_caps *caps)
^~~~~~~~~~~~~~
../drivers/cpufreq/intel_pstate.c: In function ‘intel_pstate_cppc_perf_caps’:
../drivers/cpufreq/intel_pstate.c:503:6: error: implicit declaration of function ‘cppc_get_perf_caps’; did you mean ‘get_ibs_caps’? [-Werror=implicit-function-declaration]
if (cppc_get_perf_caps(cpu->cpu, caps))
^~~~~~~~~~~~~~~~~~
get_ibs_caps
../drivers/cpufreq/intel_pstate.c:506:13: error: dereferencing pointer to incomplete type ‘struct cppc_perf_caps’
return caps->highest_perf && caps->lowest_perf <= caps->highest_perf;
^~
../drivers/cpufreq/intel_pstate.c: In function ‘intel_pstate_hybrid_hwp_calibrate’:
../drivers/cpufreq/intel_pstate.c:533:24: error: storage size of ‘caps’ isn’t known
struct cppc_perf_caps caps;
^~~~
../drivers/cpufreq/intel_pstate.c:533:24: warning: unused variable ‘caps’ [-Wunused-variable]
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
prev parent reply other threads:[~2021-05-25 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 6:39 linux-next: Tree for May 25 Stephen Rothwell
2021-05-25 17:39 ` linux-next: Tree for May 25 (x86: NR_CPUS undeclared) Randy Dunlap
2021-05-26 7:08 ` Ingo Molnar
2021-05-25 18:23 ` Randy Dunlap [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=4c20c8b0-145e-bfbf-003c-28c8eeac72dc@infradead.org \
--to=rdunlap@infradead.org \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).