linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org
Subject: OMAP build now completely broken in latest arm-soc
Date: Sun, 25 Nov 2012 09:37:04 +0000	[thread overview]
Message-ID: <20121125093704.GV3332@n2100.arm.linux.org.uk> (raw)

Not much more to say...

arch/arm/plat-omap/i2c.c:35:1: error: expected identifier or '(' before '<<' token

But also, the:

arch/arm/mach-omap2/timer.c:163:28: warning: 'omap_counter_match' defined but not used

warning is still there.

             reply	other threads:[~2012-11-25  9:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-25  9:37 Russell King - ARM Linux [this message]
2012-11-25 13:56 ` OMAP build now completely broken in latest arm-soc Olof Johansson
2012-11-25 14:07   ` Russell King - ARM Linux
2012-11-26  6:00     ` Olof Johansson
2012-11-26  8:30       ` Tomi Valkeinen
2012-11-26 17:37       ` Tony Lindgren
2012-11-27  1:13   ` 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=20121125093704.GV3332@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).