From: Arnd Bergmann <arnd@arndb•de>
To: kernel-build-reports@lists•linaro.org
Cc: "Mark Brown" <broonie@kernel•org>,
"Rafał Miłecki" <zajec5@gmail•com>,
"Hauke Mehrtens" <hauke@hauke-m•de>,
"Seiji Aguchi" <seiji.aguchi@hds•com>,
"Ard Biesheuvel" <ard.biesheuvel@linaro•org>,
"Mike Waychison" <mikew@google•com>,
"Matt Fleming" <matt.fleming@intel•com>,
linux-mips@linux-mips•org, linaro-kernel@lists•linaro.org,
linux-next@vger•kernel.org, linux-arm-kernel@lists•infradead.org
Subject: Re: next-20151013 build: 1 failures 50 warnings (next-20151013)
Date: Tue, 13 Oct 2015 14:52:42 +0200 [thread overview]
Message-ID: <10774670.W40zvvZu4L@wuerfel> (raw)
In-Reply-To: <20151013125026.GG14956@sirena.org.uk>
On Tuesday 13 October 2015 13:50:26 Mark Brown wrote:
> On Tue, Oct 13, 2015 at 11:54:09AM +0100, Build bot for Mark Brown wrote:
>
> Today's linux-next fails to build an ARM allmodconfig due to:
>
> > arm-allmodconfig
> > ../drivers/firmware/broadcom/bcm47xx_nvram.c:110:30: error: macro "DIV_ROUND_UP" requires 2 arguments, but only 1 given
> > ../drivers/firmware/broadcom/bcm47xx_nvram.c:110:4: error: 'DIV_ROUND_UP' undeclared (first use in this function)
>
> triggered by f6e734a8c16229 (MIPS: BCM47xx: Move NVRAM driver to the
> drivers/firmware/). Presumably this works due to an implicit inclusion
> on MIPS.
>
> I've CCed a lot of people listed in the changelog of the patch, though
> the list there appears somewhat random - apologies if this is irrelevant
> to you.
I've submitted a patch yesterday, see https://lkml.org/lkml/2015/10/12/303
ARnd
prev parent reply other threads:[~2015-10-13 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 10:54 next-20151013 build: 1 failures 50 warnings (next-20151013) Build bot for Mark Brown
2015-10-13 12:50 ` Mark Brown
2015-10-13 12:52 ` Arnd Bergmann [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=10774670.W40zvvZu4L@wuerfel \
--to=arnd@arndb$(echo .)de \
--cc=ard.biesheuvel@linaro$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=hauke@hauke-m$(echo .)de \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-mips@linux-mips$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=matt.fleming@intel$(echo .)com \
--cc=mikew@google$(echo .)com \
--cc=seiji.aguchi@hds$(echo .)com \
--cc=zajec5@gmail$(echo .)com \
/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