From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5901493623228058685==" MIME-Version: 1.0 From: Viresh Kumar To: kbuild-all@lists.01.org Subject: Re: [PATCH V4 3/3] thermal: cpufreq_cooling: Reuse sched_cpu_util() for SMP platforms Date: Tue, 08 Dec 2020 09:04:10 +0530 Message-ID: <20201208033410.475u3tlfplfouqtp@vireshk-i7> In-Reply-To: List-Id: --===============5901493623228058685== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 07-12-20, 11:59, Nick Desaulniers wrote: > I can see in the top commit > (https://github.com/0day-ci/linux/commit/17f0c7f4372070206925c3a10ec0e7a0= 9d03615e) > you've modified __cpufreq_cooling_register to now call > allocate_idle_time. -Wimplicit-function-declaration is observed when > calling a function for which there has been no previous declaration. > Let's look and see where or under what config allocate_idle_time is > declared, and how a randconfig might expose the missing declaration. > (The first thing I suspect is transitive header dependencies, where > some intermediary header changes what it includes based on > #define/CONFIGs, or calling a function before it's been declared). > = > It looks like allocate_idle_time is declared in the same > commit...while it's defined twice (once for CONFIG_SMP, once without), > it's not defined when CONFIG_THERMAL_GOV_POWER_ALLOCATOR is not > enabled, which is probably what the randconfig has tickled. And I was only looking only at CONFIG_SMP to see why we couldn't find a definition here :( -- = viresh --===============5901493623228058685==--