public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Koen Kooi <k.kooi@student.utwente.nl>
Cc: linux-omap@vger.kernel.org
Subject: Re: 2.6.26rc4 build error
Date: Wed, 28 May 2008 08:43:51 -0700	[thread overview]
Message-ID: <20080528154351.GX8845@atomide.com> (raw)
In-Reply-To: <9EEF473D-AA5F-49C0-875E-2D2676DCDC7C@student.utwente.nl>

Hi,

* Koen Kooi <k.kooi@student.utwente.nl> [080528 08:06]:
> Hi,
> 
> I tried building git HEAD today to get some 2.6.26rc4 goodness, but  
> stumpled upon:
> 
>    CC      arch/arm/mach-omap2/mcbsp.o
> arch/arm/mach-omap2/mcbsp.c:78: error: implicit declaration of  
> function 'IO_ADDRESS'
> arch/arm/mach-omap2/mcbsp.c:78: error: initializer element is not  
> constant
> arch/arm/mach-omap2/mcbsp.c:78: error: (near initialization for  
> 'omap2_mcbsp_pdata[0].virt_base')
> arch/arm/mach-omap2/mcbsp.c:87: error: initializer element is not  
> constant
> arch/arm/mach-omap2/mcbsp.c:87: error: (near initialization for  
> 'omap2_mcbsp_pdata[1].virt_base')
> 
> I suspect that's caused by Eduardos "MCBSP: Tranform into platform  
> driver" patches and 0001-ASoC-OMAP-Add-basic-support-for-OMAP34xx-in- 
> McBSP.patch
> 
> Does anyone have updated patches for those?

Sounds like you need to #include <linux/io.h> from mcbsp.c.

Based on the fact that it's at mach-omap2/mcbsp.o, I guess you're
trying out the unmerged mcbsp patches?

Tony

  reply	other threads:[~2008-05-28 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 15:05 2.6.26rc4 build error Koen Kooi
2008-05-28 15:43 ` Tony Lindgren [this message]
2008-05-28 15:56   ` Koen Kooi
2008-05-28 23:06   ` Koen Kooi

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=20080528154351.GX8845@atomide.com \
    --to=tony@atomide.com \
    --cc=k.kooi@student.utwente.nl \
    --cc=linux-omap@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