linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Javier Martinez Canillas <martinez.javier@gmail.com>,
	lokeshvutla@ti.com
Subject: Re: [PATCH 0/8] Flip on multiplatform support for omap2plus for v3.9
Date: Fri, 21 Dec 2012 08:48:49 -0800	[thread overview]
Message-ID: <20121221164849.GL21056@atomide.com> (raw)
In-Reply-To: <CALF0-+Xy+w=4Bs+97WJj76-tAnb56v=hS+zLyr9ue_zBKSQoVg@mail.gmail.com>

* Ezequiel Garcia <elezegarcia@gmail.com> [121221 04:50]:
> Hi Tony,
> 
> On Thu, Dec 20, 2012 at 10:05 PM, Tony Lindgren <tony@atomide.com> wrote:
> >
> > Maybe use Olof's lates pull request for fixes from LAKML +
> > ARM: l2x0: Only set .set_debug on PL310 r3p0 and earlier +
> > ARM: disable errata work-arounds which access secure registers
> > and these patches?
> >
> 
> FYI, I've successfully booted my IGEPv2 board using:
> * arm-soc/for-next

Ah right, sorry this series also needs the omap branch
omap-for-v3.8/cleanup-for-merge-window that's now in
arm-soc/for-next. Specifically it's the "ARM: OMAP: Split
fb.c to remove last remaining cpu_is_omap usage" patch.

> * igep DT patches
> * this multiplatform series
> * the two patches mentioned above
> 
> With this series CONFIG_MACH_IGEP0020 is not needed,
> just CONFIG_MACH_OMAP_GENERIC is selected.
> 
> So I guess this means, for igep v2,
> 
> Tested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>

Thanks,

Tony

  reply	other threads:[~2012-12-21 16:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 19:26 [PATCH 0/8] Flip on multiplatform support for omap2plus for v3.9 Tony Lindgren
2012-12-19 19:26 ` [PATCH 1/8] ARM: OMAP2+: Limi omap initcalls to omap only on multiplatform kernels Tony Lindgren
2012-12-19 19:26 ` [PATCH 2/8] ARM: OMAP2+: Use omap initcalls Tony Lindgren
2012-12-19 19:26 ` [PATCH 3/8] ARM: OMAP: Fix i2c cmdline initcall for multiplatform Tony Lindgren
2012-12-19 19:26 ` [PATCH 4/8] ARM: OMAP: Fix dmaengine init " Tony Lindgren
2012-12-19 19:26 ` [PATCH 5/8] ARM: OMAP2+: Add multiplatform debug_ll support Tony Lindgren
2012-12-19 19:26 ` [PATCH 6/8] ARM: OMAP2+: Disable code that currently does not work with multiplaform Tony Lindgren
2013-01-03 20:15   ` Tony Lindgren
2013-01-03 21:23     ` Laurent Pinchart
2013-01-03 22:49       ` Tony Lindgren
2013-01-03 22:53         ` Laurent Pinchart
2013-01-03 23:00           ` Tony Lindgren
2012-12-19 19:26 ` [PATCH 7/8] ARM: OMAP2+: Enable ARCH_MULTIPLATFORM support Tony Lindgren
2012-12-19 19:26 ` [PATCH 8/8] ARM: OMAP2+: Add minimal support for booting vexpress Tony Lindgren
2012-12-20 15:55 ` [PATCH 0/8] Flip on multiplatform support for omap2plus for v3.9 Tony Lindgren
2012-12-21  0:11   ` Ezequiel Garcia
2012-12-21  1:05     ` Tony Lindgren
2012-12-21 12:48       ` Ezequiel Garcia
2012-12-21 16:48         ` Tony Lindgren [this message]
2012-12-21  4:01     ` Lokesh Vutla
2012-12-21 17:48 ` [PATCH 9/8] ARM: OMAP2+: Remove now obsolete uncompress.h and debug-macro.S 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=20121221164849.GL21056@atomide.com \
    --to=tony@atomide.com \
    --cc=elezegarcia@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=martinez.javier@gmail.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).