From: Mark Brown <broonie@kernel.org>
To: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>
Subject: Re: master build: 2 failures 0 warnings (v4.10-1215-g2bfe01e)
Date: Tue, 21 Feb 2017 09:28:31 -0800 [thread overview]
Message-ID: <20170221172831.lhei7zjzmcgpcjd5@sirena.org.uk> (raw)
In-Reply-To: <E1cg4SU-0001er-8p@optimist>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
On Tue, Feb 21, 2017 at 07:01:59AM +0000, Build bot for Mark Brown wrote:
The build failures in arm and arm64 allmodconfigs that I reported in
-next last week are still present and now also appear in mainline:
> arm64-allmodconfig
> ../kernel/sched/core.c:198:25: error: 'paravirt_steal_rq_enabled' undeclared (first use in this function)
> ../kernel/sched/core.c:199:11: error: implicit declaration of function 'paravirt_steal_clock' [-Werror=implicit-function-declaration]
>
> arm-allmodconfig
> ../kernel/sched/core.c:198:25: error: 'paravirt_steal_rq_enabled' undeclared (first use in this function)
> ../kernel/sched/core.c:199:11: error: implicit declaration of function 'paravirt_steal_clock' [-Werror=implicit-function-declaration]
This is due to 004172bdad64432 (sched/core: Remove unnecessary #include
headers). asm/paravirt.h was one of the removed headers, it must be
included implicitly on x86 but clearly isn't on at least the two ARM
architectures and definitions from it are used directly. I've sent a
patch, I'll resend.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: master build: 2 failures 0 warnings (v4.10-1215-g2bfe01e)
Date: Tue, 21 Feb 2017 09:28:31 -0800 [thread overview]
Message-ID: <20170221172831.lhei7zjzmcgpcjd5@sirena.org.uk> (raw)
In-Reply-To: <E1cg4SU-0001er-8p@optimist>
On Tue, Feb 21, 2017 at 07:01:59AM +0000, Build bot for Mark Brown wrote:
The build failures in arm and arm64 allmodconfigs that I reported in
-next last week are still present and now also appear in mainline:
> arm64-allmodconfig
> ../kernel/sched/core.c:198:25: error: 'paravirt_steal_rq_enabled' undeclared (first use in this function)
> ../kernel/sched/core.c:199:11: error: implicit declaration of function 'paravirt_steal_clock' [-Werror=implicit-function-declaration]
>
> arm-allmodconfig
> ../kernel/sched/core.c:198:25: error: 'paravirt_steal_rq_enabled' undeclared (first use in this function)
> ../kernel/sched/core.c:199:11: error: implicit declaration of function 'paravirt_steal_clock' [-Werror=implicit-function-declaration]
This is due to 004172bdad64432 (sched/core: Remove unnecessary #include
headers). asm/paravirt.h was one of the removed headers, it must be
included implicitly on x86 but clearly isn't on at least the two ARM
architectures and definitions from it are used directly. I've sent a
patch, I'll resend.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170221/49e5ff7e/attachment.sig>
next parent reply other threads:[~2017-02-21 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1cg4SU-0001er-8p@optimist>
2017-02-21 17:28 ` Mark Brown [this message]
2017-02-21 17:28 ` master build: 2 failures 0 warnings (v4.10-1215-g2bfe01e) Mark Brown
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=20170221172831.lhei7zjzmcgpcjd5@sirena.org.uk \
--to=broonie@kernel.org \
--cc=efault@gmx.de \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.