linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Fannin <jfannin@gmail.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: inux-next 0701 mv643xx_eth powerpc build failure
Date: Thu, 3 Jul 2008 08:38:28 -0400	[thread overview]
Message-ID: <20080703123828.GA1631@nineveh.local> (raw)
In-Reply-To: <20080702082117.GA18989@xi.wantstofly.org>

On Wed, Jul 02, 2008 at 10:21:18AM +0200, Lennert Buytenhek wrote:
> On Tue, Jul 01, 2008 at 11:11:12PM -0400, Joseph Fannin wrote:
>
> > I'm getting a build failure on 32bit powerpc in -next, but not in mainline:
> >
> > drivers/net/mv643xx_eth.c: In function 'mv643xx_eth_netpoll':
> > drivers/net/mv643xx_eth.c:2115: error: 'INT_CAUSE_EXT' undeclared
> > (first use in this function)
> > drivers/net/mv643xx_eth.c:2115: error: (Each undeclared identifier is
> > reported only once
> > drivers/net/mv643xx_eth.c:2115: error: for each function it appears in.)
>
> Does this fix it for you?

  Yes, it builds fine.  Thanks.

>
> Index: linux-2.6.26-rc8/drivers/net/mv643xx_eth.c
> ===================================================================
> --- linux-2.6.26-rc8.orig/drivers/net/mv643xx_eth.c
> +++ linux-2.6.26-rc8/drivers/net/mv643xx_eth.c
> @@ -2184,7 +2184,7 @@ static void mv643xx_eth_netpoll(struct n
>
>  	mv643xx_eth_irq(dev->irq, dev);
>
> -	wrl(mp, INT_MASK(mp->port_num), INT_TX_END | INT_RX | INT_CAUSE_EXT);
> +	wrl(mp, INT_MASK(mp->port_num), INT_TX_END | INT_RX | INT_EXT);
>  }
>  #endif
>
>
>
> > I haven't investigated any further than a quick check if this hardware
> > even makes sense on 32bit powerpc -- it seems it does.
>
> It does -- it is used on ARM, PPC and MIPS.

--
Joseph Fannin
jfannin@gmail.com

  reply	other threads:[~2008-07-03 12:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 15:14 inux-next: Tree for July 1 Stephen Rothwell
2008-07-01 20:36 ` Rafael J. Wysocki
     [not found]   ` <200807012236.19400.rjw-KKrjLPT3xs0@public.gmane.org>
2008-07-01 20:41     ` Randy.Dunlap
2008-07-01 20:49     ` Chuck Lever
2008-07-01 21:05       ` Rafael J. Wysocki
2008-07-02  0:49   ` Trond Myklebust
2008-07-02  3:32     ` Randy Dunlap
2008-07-02 10:51       ` Rafael J. Wysocki
     [not found]     ` <76bd70e30807020734g3db408dcqea2a61622c83004d@mail.gmail.com>
2008-07-02 17:15       ` Trond Myklebust
     [not found]         ` <76bd70e30807021043x72f3aa46o8d07f2039d2ed455@mail.gmail.com>
     [not found]           ` <76bd70e30807021043x72f3aa46o8d07f2039d2ed455-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-02 19:02             ` Trond Myklebust
2008-07-02 23:14               ` Chuck Lever
2008-07-02  3:11 ` inux-next 0701 mv643xx_eth powerpc build failure Joseph Fannin
2008-07-02  4:10   ` Stephen Rothwell
2008-07-02  8:21   ` Lennert Buytenhek
2008-07-03 12:38     ` Joseph Fannin [this message]
2008-07-02  3:15 ` inux-next: Tree for July 1 Randy Dunlap
2008-07-02  3:27   ` Stephen Rothwell
2008-07-03  4:53 ` Andrew Morton
2008-07-03  4:58   ` Andrew Morton
2008-07-03  5:11     ` Andrew Morton
2008-07-03 15:36       ` Heiko Carstens

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=20080703123828.GA1631@nineveh.local \
    --to=jfannin@gmail.com \
    --cc=buytenh@wantstofly.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).