From: Mark Brown <broonie@kernel.org>
To: Pawel Moll <pawel.moll@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Build failures in -next due to use of __hrtimer_start_range_ns arm-ccn.c
Date: Wed, 13 May 2015 15:51:01 +0100 [thread overview]
Message-ID: <20150513145101.GU2761@sirena.org.uk> (raw)
In-Reply-To: <E1YsUw4-0002i4-Do@optimist>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Wed, May 13, 2015 at 12:34:48PM +0100, Build bot for Mark Brown wrote:
> arm64-allmodconfig
> ../drivers/bus/arm-ccn.c:924:3: error: implicit declaration of function '__hrtimer_start_range_ns' [-Werror=implicit-function-declaration]
>
> arm-allmodconfig
> ../drivers/bus/arm-ccn.c:924:3: error: implicit declaration of function '__hrtimer_start_range_ns' [-Werror=implicit-function-declaration]
Today's -next fails to build both arm and arm64 allmodconfig due to the
above errors, introduced in commit ffa415245b8666c44d (bus: arm-ccn:
cpumask attribute). Judging from the name of the symbol it appears that
the code is peering into hrtimer implementation details and indeed it
was removed in commit 58f1f803f1d6ef9 (hrtimer: Get rid of
__hrtimer_start_range_ns()) which has a commit message suggsting that
this has indeed been explicitly removed and no new references should be
added.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-13 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 11:34 next-20150513 build: 2 failures 47 warnings (next-20150513) Build bot for Mark Brown
2015-05-13 14:51 ` Mark Brown [this message]
2015-05-13 15:08 ` Build failures in -next due to use of __hrtimer_start_range_ns arm-ccn.c Pawel Moll
2015-05-13 15:13 ` Thomas Gleixner
2015-05-13 15:21 ` [PATCH] bus: arm-ccn: Use hrtimer_start() Pawel Moll
2015-05-13 15:32 ` Arnd Bergmann
2015-05-13 15:47 ` Pawel Moll
2015-05-13 16:19 ` Arnd Bergmann
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=20150513145101.GU2761@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=tglx@linutronix.de \
/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