linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM perf updates for 3.3
Date: Tue, 6 Dec 2011 08:52:15 -0800	[thread overview]
Message-ID: <20111206165215.GE31337@atomide.com> (raw)
In-Reply-To: <20111206000232.GC31337@atomide.com>

* Tony Lindgren <tony@atomide.com> [111205 15:34]:
> * Tony Lindgren <tony@atomide.com> [111205 14:51]:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [111205 12:40]:
> > > Tony,
> > > 
> > > Can you please treat this with the utmost urgency.  If I don't get a
> > > reply from you within the next two hours, then I'm committing this
> > > merge resolution whether or not it's correct for you - as I have other
> > > stuff which needs to be committed to my tree and I can't wait any
> > > longer for your reply.
> > 
> > Sorry only now saw this. Looking at it now.
> 
> Here's what I would do:
> 
> 1. Apply Santosh' omap2plus_defconfig patches first into devel-stable at
>    commit 53fadbdd83039bb1181e4ff76123d612cdf26c37 (Merge branch
>    'irqchip-consolidation' ...). The patches in question are 7188/1 and
>    patch 7189/1.
> 
> 2. Pull Will's for-rmk branch on top of that
> 
> 3. Run git mergetool which produces the resolution you posted earlier
> 
> 4. Before committing apply the following build fix and run git update-index
>    arch/arm/mach-omap2/display.c. This came from the DSS fixes in -rc4.
> 
> Then it all builds and boots fine. 

Added the following fix into patch system as 7194/1. Russell, can you
please apply that one into your devel-stable so we have a common
base for folks to base other omap patches on?

Regards,

Tony


From: Tony Lindgren <tony@atomide.com>
Date: Tue, 6 Dec 2011 08:46:25 -0800
Subject: [PATCH] ARM: OMAP: Fix build after a merge between v3.2-rc4 and ARM restart changes

ARM restart changes needed changes to common.h to make it local.
This conflicted with v3.2-rc4 DSS related hwmod changes that
git mergetool was not able to handle.

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

--- a/arch/arm/mach-omap2/display.c
+++ b/arch/arm/mach-omap2/display.c
@@ -22,12 +22,13 @@
 #include <linux/io.h>
 #include <linux/clk.h>
 #include <linux/err.h>
+#include <linux/delay.h>
 
 #include <video/omapdss.h>
 #include <plat/omap_hwmod.h>
 #include <plat/omap_device.h>
 #include <plat/omap-pm.h>
-#include <plat/common.h>
+#include "common.h"
 
 #include "control.h"
 #include "display.h"

  reply	other threads:[~2011-12-06 16:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 17:02 [GIT PULL] ARM perf updates for 3.3 Will Deacon
2011-12-03  9:26 ` Russell King - ARM Linux
2011-12-03 10:21   ` Will Deacon
2011-12-03 22:46     ` Russell King - ARM Linux
2011-12-05 11:23       ` Will Deacon
2011-12-05 21:11   ` Russell King - ARM Linux
2011-12-05 23:19     ` Tony Lindgren
2011-12-06  0:02       ` Tony Lindgren
2011-12-06 16:52         ` Tony Lindgren [this message]
2011-12-07 14:17           ` Cousson, Benoit
2011-12-07 15:24             ` Marc Zyngier
2011-12-07 19:44               ` 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=20111206165215.GE31337@atomide.com \
    --to=tony@atomide.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).