From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] omap4: Enable ARM local timers with OMAP4430 es1.0 exception
Date: Fri, 18 Feb 2011 23:41:34 +0530 [thread overview]
Message-ID: <33e02589041f47e8df8bdc7d97a631f1@mail.gmail.com> (raw)
In-Reply-To: <1297510187-31547-3-git-send-email-santosh.shilimkar@ti.com>
> -----Original Message-----
> From: Santosh Shilimkar [mailto:santosh.shilimkar at ti.com]
> Sent: Saturday, February 12, 2011 5:00 PM
> To: linux-omap at vger.kernel.org
> Cc: khilman at ti.com; linux-arm-kernel at lists.infradead.org;
> tony at atomide.com; Santosh Shilimkar
> Subject: [PATCH 2/5] omap4: Enable ARM local timers with OMAP4430
> es1.0 exception
>
[....]
> diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-
> omap2/Kconfig
> index 1a2cf62..f285dd7 100644
> --- a/arch/arm/mach-omap2/Kconfig
> +++ b/arch/arm/mach-omap2/Kconfig
> @@ -44,6 +44,7 @@ config ARCH_OMAP4
> depends on ARCH_OMAP2PLUS
> select CPU_V7
> select ARM_GIC
> + select LOCAL_TIMERS
This change should be 'select LOCAL_TIMERS if SMP'
Otherwise, with !SMP, the build will break.
Here is the updated version with Tony's ack added.
--------
next prev parent reply other threads:[~2011-02-18 18:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 11:29 [PATCH 0/5] ARM: omap4 related fixes for 2.6.39 Santosh Shilimkar
2011-02-12 11:29 ` [PATCH 1/5] ARM: smp: Select local timers vs dummy timer support runtime Santosh Shilimkar
2011-02-15 4:13 ` David Brown
2011-02-15 4:15 ` David Brown
2011-02-16 12:45 ` Santosh Shilimkar
2011-02-20 11:03 ` Russell King - ARM Linux
2011-02-20 11:07 ` [PATCH 1/5] ARM: smp: Select local timers vs dummy timersupport runtime Santosh Shilimkar
2011-02-23 16:36 ` Russell King - ARM Linux
2011-02-23 16:38 ` [PATCH 1/5] ARM: smp: Select local timers vs dummytimersupport runtime Santosh Shilimkar
2011-02-23 17:58 ` Santosh Shilimkar
2011-02-23 19:03 ` Russell King - ARM Linux
2011-02-23 19:11 ` [PATCH 1/5] ARM: smp: Select local timers vs dummytimersupportruntime Santosh Shilimkar
2011-02-23 19:55 ` Russell King - ARM Linux
2011-02-23 20:04 ` [PATCH 1/5] ARM: smp: Select local timers vsdummytimersupportruntime Santosh Shilimkar
2011-02-12 11:29 ` [PATCH 2/5] omap4: Enable ARM local timers with OMAP4430 es1.0 exception Santosh Shilimkar
2011-02-14 21:08 ` Tony Lindgren
2011-02-18 18:11 ` Santosh Shilimkar [this message]
2011-02-12 11:29 ` [PATCH 3/5] ARM: l2x0: Errata fix for flush by Way operation can cause data corruption Santosh Shilimkar
2011-02-12 17:50 ` Andrei Warkentin
2011-02-12 17:59 ` Santosh Shilimkar
2011-02-12 23:17 ` Andrei Warkentin
2011-02-14 5:08 ` Santosh Shilimkar
2011-02-14 19:33 ` Andrei Warkentin
2011-02-14 21:06 ` Andrei Warkentin
2011-02-15 7:14 ` Santosh Shilimkar
2011-02-15 9:10 ` Andrei Warkentin
2011-02-15 9:30 ` Santosh Shilimkar
2011-02-16 12:32 ` Santosh Shilimkar
2011-02-16 15:53 ` Catalin Marinas
2011-02-16 15:58 ` Santosh Shilimkar
2011-02-18 12:02 ` Santosh Shilimkar
2011-02-12 11:29 ` [PATCH 4/5] omap2plus: omap4: Set NR_CPU to 2 instead of default 4 Santosh Shilimkar
2011-02-14 21:09 ` Tony Lindgren
2011-02-12 11:29 ` [PATCH 5/5] omap4: Remove 'FIXME: omap44xx_sram_init not implemented' Santosh Shilimkar
2011-02-14 21:09 ` 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=33e02589041f47e8df8bdc7d97a631f1@mail.gmail.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).