public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20151013 build: 1 failures 50 warnings (next-20151013)
Date: Tue, 13 Oct 2015 13:50:26 +0100	[thread overview]
Message-ID: <20151013125026.GG14956@sirena.org.uk> (raw)
In-Reply-To: <E1ZlxDc-0000ea-U4@optimist>

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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151013/3c3ac2ef/attachment.sig>

       reply	other threads:[~2015-10-13 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1ZlxDc-0000ea-U4@optimist>
2015-10-13 12:50 ` Mark Brown [this message]
2015-10-13 12:52   ` next-20151013 build: 1 failures 50 warnings (next-20151013) 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=20151013125026.GG14956@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox