From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org, David Vrabel <david.vrabel@csr.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: usb/sparc build failure
Date: Wed, 28 May 2008 09:19:59 +1000 [thread overview]
Message-ID: <20080528091959.1d527095.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080527165019.GB3699@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Hi Greg,
On Tue, 27 May 2008 09:50:19 -0700 Greg KH <greg@kroah.com> wrote:
>
> On Tue, May 27, 2008 at 08:26:30PM +1000, Stephen Rothwell wrote:
> >
> > drivers/uwb/whci.c:166: error: `DMA_64BIT_MASK' undeclared (first use in this function)
> > drivers/uwb/whci.c:166: error: (Each undeclared identifier is reported only once
> > drivers/uwb/whci.c:166: error: for each function it appears in.)
> > drivers/uwb/whci.c:168: error: `DMA_32BIT_MASK' undeclared (first use in this function)
>
> Is this sparc64 or sparc32? I don't seem to get these errors using the
> sparc64 cross compiler tool chain.
http://kisskb.ellerman.id.au/kisskb/buildresult/29187/ (that's from the
day before yesterday, but it happened again yesterday). sparc32 build
using a biarch sparc64 cross compiler.
But it shouldn't matter. If you use something from a header file,
include it (or something that is guaranteed to include it on all
architecture using all configs).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-27 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 10:26 linux-next: usb/sparc build failure Stephen Rothwell
2008-05-27 16:50 ` Greg KH
2008-05-27 23:19 ` Stephen Rothwell [this message]
2008-05-27 17:41 ` David Vrabel
2008-05-27 18:02 ` Greg KH
2008-05-27 23:25 ` Stephen Rothwell
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=20080528091959.1d527095.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=david.vrabel@csr.com \
--cc=greg@kroah.com \
--cc=linux-next@vger.kernel.org \
/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).