public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Varadarajan, Charulatha" <charu@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Nayak, Rajendra" <rnayak@ti.com>
Subject: Re: compilation error on hwmods branch
Date: Wed, 17 Mar 2010 10:45:02 -0700	[thread overview]
Message-ID: <877hpargf5.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100317170348.GD2900@atomide.com> (Tony Lindgren's message of "Wed\, 17 Mar 2010 10\:03\:48 -0700")

Tony Lindgren <tony@atomide.com> writes:

> * Varadarajan, Charulatha <charu@ti.com> [100317 08:09]:
>> In "origin/pm-wip/hwmods" branch, using "omap_3430sdp_defconfig" or  "omap3_defconfig", results in the following error. 
>> Anyone working on this?
>> 
>> drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' before 'do'
>> drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' before 'while'
>> drivers/usb/musb/omap2430.c:268: error: expected identifier or '(' before 'do'
>> drivers/usb/musb/omap2430.c:268: error: expected identifier or '(' before 'while'
>> make[2]: *** [drivers/usb/musb/omap2430.o] Error 1
>> make[1]: *** [drivers/usb/musb] Error 2
>> make: *** [drivers] Error 2
>
> A fix for that has been already queued via linux-usb. Also in
> omap-testing and master branches.

Hi Charu,

pm-wip/hwmods branch is currently based at v2.6.34-rc1 for ease of
merging with other development trees.

If you want to test with this, please merge it into l-o master or the
PM branch which both include fixes for various problems as Tony
mentioned.

Kevin


  reply	other threads:[~2010-03-17 17:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 13:37 [PATCH 0/4 RFC]OMAP:GPIO: Make GPIO an early init device Varadarajan, Charulatha
2010-02-12 13:37 ` [PATCH 1/4 RFC]OMAP2: Fix compile errors Varadarajan, Charulatha
     [not found]   ` <1265981851-11970-3-git-send-email-charu@ti.com>
2010-02-12 13:37     ` [PATCH 3/4 RFC]OMAP:Convert GPIO into a early driver Varadarajan, Charulatha
2010-02-12 13:37       ` [PATCH 4/4 RFC]OMAP:GPIO: Convert all printk's to pr_* in gpio Varadarajan, Charulatha
2010-02-16 23:15   ` [PATCH 1/4 RFC]OMAP2: Fix compile errors Kevin Hilman
2010-03-17 15:12     ` compilation error on hwmods branch Varadarajan, Charulatha
2010-03-17 17:03       ` Tony Lindgren
2010-03-17 17:45         ` Kevin Hilman [this message]
2010-02-12 22:31 ` [PATCH 0/4 RFC]OMAP:GPIO: Make GPIO an early init device Paul Walmsley
2010-02-15  1:38   ` Paul Walmsley
2010-02-15 17:49     ` Tony Lindgren
2010-02-16 15:06       ` Varadarajan, Charulatha
2010-02-16 19:46         ` Tony Lindgren
2010-03-17 14:10           ` Varadarajan, Charulatha
2010-03-17 23:19             ` 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=877hpargf5.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=charu@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.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