From: Mark Brown <broonie@kernel•org>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel•com>,
Viresh Kumar <viresh.kumar@linaro•org>,
"Gautham R. Shenoy" <ego@linux•vnet.ibm.com>
Cc: kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
linux-pm@vger•kernel.org
Subject: Re: next-20160210 build: 2 failures 4 warnings (next-20160210)
Date: Wed, 10 Feb 2016 09:52:52 +0000 [thread overview]
Message-ID: <20160210095252.GS13270@sirena.org.uk> (raw)
In-Reply-To: <E1aTQoy-0005cH-Tr@optimist>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
On Wed, Feb 10, 2016 at 09:12:25AM +0000, Build bot for Mark Brown wrote:
Today's -next fails to build on non-SMP configurations due to:
> arm-multi_v5_defconfig
> ../drivers/cpufreq/cpufreq_governor.c:251:3: error: implicit declaration of function 'irq_work_queue_on' [-Werror=implicit-function-declaration]
caused by 0144fa03ef4606ae (cpufreq: governor: Replace timers with
utilization update callbacks). IS_ENABLED() in an if statement doesn't
do a good job of making things conditional here since the code still has
to compile cleanly in both cases and there is no definition at all of
irq_work_queue_on() for !SMP.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-02-10 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 9:12 next-20160210 build: 2 failures 4 warnings (next-20160210) Build bot for Mark Brown
2016-02-10 9:52 ` Mark Brown [this message]
2016-02-10 14:27 ` Rafael J. Wysocki
2016-02-10 15:04 ` Arnd Bergmann
2016-02-10 15:07 ` [PATCH] irq_work: unhide irq_work_queue_on declaration on non-SMP Arnd Bergmann
2016-02-10 15:27 ` Rafael J. Wysocki
2016-02-10 18:10 ` Mark Brown
2016-02-10 10:08 ` next-20160210 build: 2 failures 4 warnings (next-20160210) Mark Brown
2016-02-10 10:12 ` Will Deacon
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=20160210095252.GS13270@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=ego@linux$(echo .)vnet.ibm.com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=rafael.j.wysocki@intel$(echo .)com \
--cc=viresh.kumar@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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