public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Tony Lindgren <tony@atomide.com>
Cc: me@felipebalbi.com, "Gadiyar, Anand" <gadiyar@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] Fix compile error in usb-musb.c
Date: Mon, 26 Jan 2009 15:23:42 -0800	[thread overview]
Message-ID: <200901261523.42769.david-b@pacbell.net> (raw)
In-Reply-To: <20090118113324.GC7976@atomide.com>

On Sunday 18 January 2009, Tony Lindgren wrote:
> 
> > > #if     !defined(CONFIG_ARCH_OMAP730) && \
> > >     !defined(CONFIG_ARCH_OMAP15XX) && \
> > >     !defined(CONFIG_ARCH_OMAP16XX) && \
> > >     !defined(CONFIG_ARCH_OMAP24XX) && \
> > >     !defined(CONFIG_ARCH_OMAP34XX)
> > > #error "Power management for this processor not implemented yet"
> > > #endif
> > 
> > I didn't realize anyone outside of TI had their hands
> > on OMAP4 chips yet.  :)
> 
> Might be worth looking what it would take to make dummy CONFIG_PM
> compile in mainline for mach-omap2.

This (against mainline) makes build+link work ...


---
 arch/arm/plat-omap/include/mach/pm.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/arch/arm/plat-omap/include/mach/pm.h
+++ b/arch/arm/plat-omap/include/mach/pm.h
@@ -108,7 +108,7 @@
 	!defined(CONFIG_ARCH_OMAP15XX) && \
 	!defined(CONFIG_ARCH_OMAP16XX) && \
 	!defined(CONFIG_ARCH_OMAP24XX)
-#error "Power management for this processor not implemented yet"
+#warning "Power management for this processor not implemented yet"
 #endif
 
 #ifndef __ASSEMBLER__

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-01-26 23:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 18:48 [PATCH] Fix compile error in usb-musb.c Gadiyar, Anand
2009-01-16  7:29 ` Tony Lindgren
2009-01-16  7:37   ` Tony Lindgren
2009-01-16 15:35     ` Felipe Balbi
2009-01-16 15:38       ` Gadiyar, Anand
2009-01-16 15:49         ` Felipe Balbi
2009-01-16 15:54           ` Gadiyar, Anand
2009-01-16 21:27       ` David Brownell
2009-01-16 22:19         ` Felipe Balbi
2009-01-16 22:31           ` David Brownell
2009-01-16 22:41             ` Felipe Balbi
2009-01-18 11:33             ` Tony Lindgren
2009-01-26 23:23               ` David Brownell [this message]
2009-01-26 23:26                 ` Felipe Balbi
2009-02-12  1:24                 ` Tony Lindgren
2009-02-12  1:55                   ` David Brownell
2009-02-12 21:35                     ` Tony Lindgren

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=200901261523.42769.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.com \
    --cc=tony@atomide.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