From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20150323 build: 1 failures 23 warnings (next-20150323)
Date: Mon, 23 Mar 2015 14:25:24 -0700 [thread overview]
Message-ID: <20150323212524.GU14954@sirena.org.uk> (raw)
In-Reply-To: <E1YZyoN-00019n-50@debutante>
On Mon, Mar 23, 2015 at 09:38:19AM +0000, Build bot for Mark Brown wrote:
In current -next the bgmac driver does not compile in an ARM
allmodconfig:
> arm-allmodconfig
> ../drivers/net/ethernet/broadcom/bgmac.c:20:27: fatal error: bcm47xx_nvram.h: No such file or directory
because this include file is only present on MIPS. This looks at first
glance to have happened in the merge commit edb15d83a875a1f4 from the
MIPS tree though I think that needs a bit more investigation.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150323/93bc3c5f/attachment.sig>
next parent reply other threads:[~2015-03-23 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YZyoN-00019n-50@debutante>
2015-03-23 21:25 ` Mark Brown [this message]
2015-03-23 22:08 ` next-20150323 build: 1 failures 23 warnings (next-20150323) Ralf Baechle
2015-03-23 22:16 ` Rafał Miłecki
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=20150323212524.GU14954@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