From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Brown <mbrown@fensystems.co.uk>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: sfx.c driver build failure
Date: Fri, 25 Jul 2008 17:50:57 +1000 [thread overview]
Message-ID: <1216972257.11188.96.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.62.0807250831440.8217@dolphin.home>
On Fri, 2008-07-25 at 08:35 +0100, Michael Brown wrote:
> On Fri, 25 Jul 2008, Benjamin Herrenschmidt wrote:
> > The sfx driver (which happens to be part of some of our test configs)
> > fails to build in current Linus tree on powerpc with this error:
> >
> > /home/benh/kernels/linux-powerpc/drivers/net/sfc/efx.c: In function ÿÿefx_probe_interruptsÿÿ:
> > /home/benh/kernels/linux-powerpc/drivers/net/sfc/efx.c:845: error: lvalue required as unary ÿÿ&ÿÿ oper
> > and
>
> I'm not the maintainer of that code; I wrote the original version, but
> it's now maintained by Solarflare.
>
> I don't see anything on that line that ought to be architecture-specific.
> Could you send me the preprocessed efx.c from your powerpc build?
Apparently, it's a know generic breakage of the topology stuff,
it's beeing sorted out.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Brown <mbrown@fensystems.co.uk>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: sfx.c driver build failure
Date: Fri, 25 Jul 2008 17:50:57 +1000 [thread overview]
Message-ID: <1216972257.11188.96.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.62.0807250831440.8217@dolphin.home>
On Fri, 2008-07-25 at 08:35 +0100, Michael Brown wrote:
> On Fri, 25 Jul 2008, Benjamin Herrenschmidt wrote:
> > The sfx driver (which happens to be part of some of our test configs)
> > fails to build in current Linus tree on powerpc with this error:
> >
> > /home/benh/kernels/linux-powerpc/drivers/net/sfc/efx.c: In function ÿÿefx_probe_interruptsÿÿ:
> > /home/benh/kernels/linux-powerpc/drivers/net/sfc/efx.c:845: error: lvalue required as unary ÿÿ&ÿÿ oper
> > and
>
> I'm not the maintainer of that code; I wrote the original version, but
> it's now maintained by Solarflare.
>
> I don't see anything on that line that ought to be architecture-specific.
> Could you send me the preprocessed efx.c from your powerpc build?
Apparently, it's a know generic breakage of the topology stuff,
it's beeing sorted out.
Cheers,
Ben.
next prev parent reply other threads:[~2008-07-25 7:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 6:15 sfx.c driver build failure Benjamin Herrenschmidt
2008-07-25 6:15 ` Benjamin Herrenschmidt
2008-07-25 7:17 ` Stephen Rothwell
2008-07-25 7:17 ` Stephen Rothwell
2008-07-25 7:32 ` Ingo Molnar
2008-07-25 7:32 ` Ingo Molnar
2008-07-25 7:35 ` Michael Brown
2008-07-25 7:35 ` Michael Brown
2008-07-25 7:50 ` Benjamin Herrenschmidt [this message]
2008-07-25 7:50 ` Benjamin Herrenschmidt
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=1216972257.11188.96.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mbrown@fensystems.co.uk \
/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.