From: Ralf Baechle <ralf@linux-mips.org>
To: Mark Brown <broonie@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
"Rafał Miłecki" <zajec5@gmail.com>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
linux-mips@linux-mips.org
Subject: Re: next-20150323 build: 1 failures 23 warnings (next-20150323)
Date: Mon, 23 Mar 2015 23:08:07 +0100 [thread overview]
Message-ID: <20150323220806.GB8891@linux-mips.org> (raw)
In-Reply-To: <20150323212524.GU14954@sirena.org.uk>
On Mon, Mar 23, 2015 at 02:25:24PM -0700, Mark Brown wrote:
> 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.
At that time the bgmac NIC was still exclusivly used on MIPS.
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: ralf@linux-mips.org (Ralf Baechle)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20150323 build: 1 failures 23 warnings (next-20150323)
Date: Mon, 23 Mar 2015 23:08:07 +0100 [thread overview]
Message-ID: <20150323220806.GB8891@linux-mips.org> (raw)
In-Reply-To: <20150323212524.GU14954@sirena.org.uk>
On Mon, Mar 23, 2015 at 02:25:24PM -0700, Mark Brown wrote:
> 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.
At that time the bgmac NIC was still exclusivly used on MIPS.
Ralf
next prev parent reply other threads:[~2015-03-23 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YZyoN-00019n-50@debutante>
2015-03-23 21:25 ` next-20150323 build: 1 failures 23 warnings (next-20150323) Mark Brown
2015-03-23 21:25 ` Mark Brown
2015-03-23 22:08 ` Ralf Baechle [this message]
2015-03-23 22:08 ` Ralf Baechle
2015-03-23 22:16 ` Rafał Miłecki
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=20150323220806.GB8891@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=zajec5@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.