From: Mel Gorman <mgorman@suse.de>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
juri.lelli@redhat.com,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
rostedt@goodmis.org, bsegall@google.com,
lkft-triage@lists.linaro.org, anshuman.khandual@arm.com
Subject: Re: kernel/sched/fair.c:1524:20: warning: ???test_idle_cores??? declared ???static??? but never defined
Date: Tue, 3 Mar 2020 10:39:41 +0000 [thread overview]
Message-ID: <20200303103941.GD3772@suse.de> (raw)
In-Reply-To: <CA+G9fYtE-=odd9OLrGim-D1hqgrMaoxqpGSvXCNLfAicdxS8jA@mail.gmail.com>
On Tue, Mar 03, 2020 at 02:42:38PM +0530, Naresh Kamboju wrote:
> Linux next-20200303 arm64 build warnings
> Please refer below links for more information.
>
> make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j16 ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu- HOSTCC=gcc CC="sccache
> aarch64-linux-gnu-gcc" O=build Image
>
> ../kernel/sched/fair.c:1524:20: warning: ???test_idle_cores??? declared
> ???static??? but never defined [-Wunused-function]
> 1524 | static inline bool test_idle_cores(int cpu, bool def);
> | ^~~~~~~~~~~~~~~
>
There is a fix posted that addresses this but it has not reached
tip/sched/core. I'll resend the accumulated fixes today and cc you.
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2020-03-03 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 9:12 kernel/sched/fair.c:1524:20: warning: ‘test_idle_cores’ declared ‘static’ but never defined Naresh Kamboju
2020-03-03 10:39 ` Mel Gorman [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=20200303103941.GD3772@suse.de \
--to=mgorman@suse.de \
--cc=anshuman.khandual@arm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mingo@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.