netdev - Re: [PATCH] bgmac: make bgmac depend on bcm47xx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 24 Jul 2013 09:54:12 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Hauke Mehrtens <hauke@...ke-m.de>, davem@...emloft.net,
	zajec5@...il.com, netdev@...r.kernel.org,
	linux-next@...r.kernel.org
Subject: Re: [PATCH] bgmac: make bgmac depend on bcm47xx

On Wed, Jul 24, 2013 at 11:08:58AM +1000, Stephen Rothwell wrote:
> Hi,
> 
> On Tue, 23 Jul 2013 23:28:49 +0200 Hauke Mehrtens <hauke@...ke-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@...ke-m.de>
> > Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
> 
> This patch really needs to go to John as the patch that exposes the
> breakage is in his tree.

I'll merge this one -- OK, Dave?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html