From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL REQUEST] big-endian updates for ARM
Date: Tue, 03 Sep 2013 13:51:40 +0100 [thread overview]
Message-ID: <5225DB5C.1070903@codethink.co.uk> (raw)
In-Reply-To: <20130903134546.5240306b@skate>
On 03/09/13 12:45, Thomas Petazzoni wrote:
> Dear Ben Dooks,
>
> On Tue, 03 Sep 2013 12:25:08 +0100, Ben Dooks wrote:
>
>> Sorry, I thought that had been fixed, thanks for reminding me.
>>
>> I have fixed it and now on:
>>
>> git://git.baserock.org/delta/linux baserock/311-rc7/be/core-v4
>
> Can you resend a proper pull request for this core-v4 branch? There has
> been two fixes since the v3, the Acked-by from one of the mach-mvebu
> maintainers, and my Tested-by.
that was just a confirmation for Dave to test. I will sort out a new
pull request later.
> Also, as indicated on IRC, I confirm that this patch set also works on
> Armada 370. It doesn't work on one particular Armada 370 board that I
> have, but it's using an old bootloader that may be the cause of the
> issue. The BE kernel works fine on the two other Armada 370 boards I've
> tested.
>
> Thanks!
>
> Thomas
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2013-09-03 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130903101332.GA26613@localhost.localdomain>
2013-09-03 11:25 ` [PULL REQUEST] big-endian updates for ARM Ben Dooks
2013-09-03 11:45 ` Thomas Petazzoni
2013-09-03 12:51 ` Ben Dooks [this message]
2013-09-03 12:55 ` Thomas Petazzoni
2013-09-03 15:21 ` Ben Dooks
2013-09-03 15:29 ` Thomas Petazzoni
2013-09-02 11:24 Ben Dooks
2013-09-02 11:27 ` Thomas Petazzoni
2013-09-02 11:32 ` Ben Dooks
2013-09-02 11:51 ` Thomas Petazzoni
2013-09-02 17:22 ` Jason Cooper
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=5225DB5C.1070903@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--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).