From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: v3.10 - big endian core support
Date: Mon, 15 Jul 2013 15:17:12 +0200 [thread overview]
Message-ID: <20130715151712.69f2cf8d@skate> (raw)
In-Reply-To: <51E3CE41.5010807@codethink.co.uk>
Dear Ben Dooks,
On Mon, 15 Jul 2013 11:26:09 +0100, Ben Dooks wrote:
> I've pushed out two new branches on git.baserock.org/delta/linux.git
> as:
> baserock/311/be/core-v2
> baserock/311/be/atags-v2
I've tested baserock/311/be/core-v2, after rebasing it on top of
3.11-rc1. I've tested the following combination on an Armada XP board:
little endian ARM, big endian ARM, little endian Thumb2 and big endian
Thumb2. They all worked fine.
There were minor conflicts in arch/arm/kernel/sleep.S and
arch/arm/mach-mvebu/headsmp.S when doing the rebase on top of 3.11-rc1,
but nothing major.
Ben, do you have the time to rebase on 3.11-rc1 and post the patches
for merging?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-07-15 13:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALicx6u89THSiRa4FzGZrcoG8q+o_BD8qVEC4CYXEjPUVK_fJw@mail.gmail.com>
2013-07-12 11:47 ` v3.10 - big endian core support Thomas Petazzoni
2013-07-12 11:56 ` Vijay Kilari
2013-07-12 12:00 ` Ben Dooks
2013-07-15 2:50 ` jgq516 at gmail.com
2013-07-15 6:15 ` Vijay Kilari
2013-07-12 11:58 ` Ben Dooks
2013-07-12 12:06 ` Thomas Petazzoni
2013-07-12 12:33 ` Ben Dooks
2013-07-14 21:53 ` Will Deacon
2013-07-15 8:03 ` Ben Dooks
2013-07-15 8:36 ` Thomas Petazzoni
2013-07-15 9:02 ` jgq516 at gmail.com
2013-07-15 10:26 ` Ben Dooks
2013-07-15 13:17 ` Thomas Petazzoni [this message]
2013-07-16 8:00 ` jgq516 at gmail.com
2013-07-16 10:38 ` Ben Dooks
2013-07-01 11:03 Ben Dooks
2013-07-01 14:33 ` Thomas Petazzoni
2013-07-01 15:20 ` Ben Dooks
2013-07-08 5:39 ` jgq516 at gmail.com
2013-07-08 8:49 ` Will Deacon
2013-07-08 9:51 ` jgq516 at gmail.com
2013-07-08 11:02 ` Will Deacon
2013-07-08 17:03 ` Will Deacon
2013-07-09 1:18 ` jgq516 at gmail.com
2013-07-09 3:34 ` jgq516 at gmail.com
2013-07-09 7:45 ` Will Deacon
2013-07-09 9:55 ` jgq516 at gmail.com
2013-07-09 10:04 ` jgq516 at gmail.com
2013-07-09 15:36 ` Thomas Petazzoni
2013-07-08 9:58 ` Ben Dooks
2013-07-08 10:03 ` jgq516 at gmail.com
2013-07-08 11:10 ` Ben Dooks
2013-07-09 9:53 ` jgq516 at gmail.com
2013-07-09 9:59 ` Ben Dooks
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=20130715151712.69f2cf8d@skate \
--to=thomas.petazzoni@free-electrons.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 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.