From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: davem@davemloft.net, zajec5@gmail.com, netdev@vger.kernel.org,
linville@tuxdriver.com, linux-next@vger.kernel.org
Subject: Re: [PATCH] bgmac: make bgmac depend on bcm47xx
Date: Wed, 24 Jul 2013 13:26:01 +1000 [thread overview]
Message-ID: <20130724132601.94633488e3cb8a3b84267247@canb.auug.org.au> (raw)
In-Reply-To: <20130724110858.01e033323d739cf6b998e2ea@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
Hi,
On Wed, 24 Jul 2013 11:08:58 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Tue, 23 Jul 2013 23:28:49 +0200 Hauke Mehrtens <hauke@hauke-m.de> wrote:
> >
> > bgmac uses bcm47xx_nvram.h which is only available when BCM47XX was
> > selected. Earlier BCMA_HOST_SOC depended on BCM47XX so this was not
> > build on any other archs, but that changed. We should modify this
> > driver to get access to the nvram or the variables through platform
> > data.
> >
> > This fixes a build problem in linux-next reported by Stephen Rothwell:
> >
> > drivers/net/ethernet/broadcom/bgmac.c:19:27: fatal error: bcm47xx_nvram.h: No such file or directory
> > #include <bcm47xx_nvram.h>
> > ^
> >
> > Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>
> This patch really needs to go to John as the patch that exposes the
> breakage is in his tree.
I applied this to the wireless-next tree merge today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-24 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 21:28 [PATCH] bgmac: make bgmac depend on bcm47xx Hauke Mehrtens
2013-07-24 1:08 ` Stephen Rothwell
2013-07-24 3:26 ` Stephen Rothwell [this message]
2013-07-24 13:54 ` John W. Linville
2013-07-24 19:40 ` David Miller
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=20130724132601.94633488e3cb8a3b84267247@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=hauke@hauke-m.de \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).