netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: sfr@canb.auug.org.au, hauke@hauke-m.de, zajec5@gmail.com,
	netdev@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH] bgmac: make bgmac depend on bcm47xx
Date: Wed, 24 Jul 2013 12:40:59 -0700 (PDT)	[thread overview]
Message-ID: <20130724.124059.1161220675165309031.davem@davemloft.net> (raw)
In-Reply-To: <20130724135409.GA2385@tuxdriver.com>

From: "John W. Linville" <linville@tuxdriver.com>
Date: Wed, 24 Jul 2013 09:54:12 -0400

> 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@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'll merge this one -- OK, Dave?

No problem.

      reply	other threads:[~2013-07-24 19:41 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
2013-07-24 13:54   ` John W. Linville
2013-07-24 19:40     ` David Miller [this message]

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=20130724.124059.1161220675165309031.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=hauke@hauke-m.de \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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).