linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/03] ARM: 64-bit memory fixes, APE6EVM second memory bank
Date: Wed, 12 Jun 2013 10:57:16 +0000	[thread overview]
Message-ID: <CANqRtoSZXz5-z4pMTM_gpTf11qQCc870Vf35qLQ4jpoCPnq4KQ@mail.gmail.com> (raw)
In-Reply-To: <201306051317.02284.arnd@arndb.de>

Hi Arnd,

On Wed, Jun 5, 2013 at 8:17 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Wednesday 05 June 2013, Magnus Damm wrote:
>> ARM: 64-bit memory fixes, APE6EVM second memory bank
>>
>> [PATCH 01/03] ARM: Let arm_add_memory() always use 64-bit arguments
>> [PATCH 02/03] ARM: Handle 64-bit memory in case of 32-bit phys_addr_t
>> [PATCH 03/03] ARM: shmobile: Add second memory bank to DTS for APE6EVM
>>
>> This patch set contains two fixes and one mach-shmobile specific patch
>> to add a second memory bank. The fixes attempt to improve the memory bank
>> handling in the ARM kernel in case of 64-bit addresses.
>
> Please have a look at this patch that Stepan Moskovchenko posted:
>
> https://patchwork.kernel.org/patch/2639171/
>
> I think we are going to need only one of the two approaches.

Thanks for pointing out this implementation. Is there anything I can
do to move this forward?

Cheers,

/ magnus

  reply	other threads:[~2013-06-12 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 10:44 [PATCH 00/03] ARM: 64-bit memory fixes, APE6EVM second memory bank Magnus Damm
2013-06-05 10:44 ` [PATCH 01/03] ARM: Let arm_add_memory() always use 64-bit arguments Magnus Damm
2013-06-05 10:44 ` [PATCH 02/03] ARM: Handle 64-bit memory in case of 32-bit phys_addr_t Magnus Damm
2013-06-05 10:44 ` [PATCH 03/03] ARM: shmobile: Add second memory bank to DTS for APE6EVM Magnus Damm
2013-06-05 11:17 ` [PATCH 00/03] ARM: 64-bit memory fixes, APE6EVM second memory bank Arnd Bergmann
2013-06-12 10:57   ` Magnus Damm [this message]
2013-06-12 12:41     ` Arnd Bergmann
2013-07-02  5:52       ` Magnus Damm
2013-06-17 12:44 ` Guennadi Liakhovetski

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=CANqRtoSZXz5-z4pMTM_gpTf11qQCc870Vf35qLQ4jpoCPnq4KQ@mail.gmail.com \
    --to=magnus.damm@gmail.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).