All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hemanth V" <hemanthv@ti.com>
To: linux-omap@vger.kernel.org
Subject: L-O master branch broken ?
Date: Thu, 18 Jun 2009 15:05:11 +0530	[thread overview]
Message-ID: <00eb01c9eff8$13dba760$LocalHost@wipultra793> (raw)

I get the below error while compiling 3430SDP. I see below commit  as the 
latest one.

Hemanth

commit 3dc15d62d3f8e85d74dcbabc234585cb8dbc2194
Author: Tony Lindgren <tony@atomide.com>
Date:   Thu Jun 18 08:59:09 2009 +0300

    Fix iommu.c file permissions

    Commit c8c8bfc4c3664317441b0037040c9bdea210fba1 changed the
    permissions, so undo that. Also checked the other files with:

    $ find arch/arm/*omap* -type f -perm 755

    Signed-off-by: Tony Lindgren <tony@atomide.com>


arch/arm/plat-omap/sram.c: In function 'omap_detect_sram':
arch/arm/plat-omap/sram.c:139: error: expected expression before 'else'
arch/arm/plat-omap/sram.c:190: warning: ISO C90 forbids mixed declarations 
and code
arch/arm/plat-omap/sram.c:347: error: invalid storage class for function 
'omap242x_sram_init'
arch/arm/plat-omap/sram.c:368: error: invalid storage class for function 
'omap243x_sram_init'
arch/arm/plat-omap/sram.c:433: error: expected declaration or statement at 
end of input
make[1]: *** [arch/arm/plat-omap/sram.o] Error 1
make: *** [arch/arm/plat-omap] Error 2


             reply	other threads:[~2009-06-18  9:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  9:35 Hemanth V [this message]
2009-06-18  7:52 ` L-O master branch broken ? Tony Lindgren
2009-06-18 10:38   ` Hemanth V
2009-06-18 10:22     ` Tony Lindgren
2009-06-18 14:47       ` Hemanth V
2009-06-18 15:31         ` Kevin Hilman
2009-06-18 23:10           ` Aguirre Rodriguez, Sergio Alberto

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='00eb01c9eff8$13dba760$LocalHost@wipultra793' \
    --to=hemanthv@ti.com \
    --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 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.