From: robert.richter@caviumnetworks.com (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 00/10] arm64, numa: Add numa support for arm64 platforms
Date: Sat, 20 Feb 2016 11:39:59 +0100 [thread overview]
Message-ID: <20160220103959.GC4914@rric.localdomain> (raw)
In-Reply-To: <CAKv+Gu8FRdif_WDZPqs7gHxXMu=6SqDd6A54dQc1KWuGwxpf0w@mail.gmail.com>
On 20.02.16 09:20:05, Ard Biesheuvel wrote:
> On 20 February 2016 at 02:13, David Daney <ddaney.cavm@gmail.com> wrote:
> > From: David Daney <david.daney@cavium.com>
> >
> > v11:
> > - Dropped cleanup patches for other architectures, they will be
> > submitted as a separate set after more testing.
> >
> > - Added patch set from Ard Biesheuvel that are needed to make
> > the whole thing actually work. Previously this was a
> > separate set.
> >
>
> This series is out of date, unfortunately. The EFI init code is now
> (as of v4.5-rc1) shared between ARM and arm64, which means that any
> changes you make must be made on both sides. This applies to the split
> between parsing the EFI dt nodes and performing the actual EFI init,
> but also to the early_init_dt_add_memory_arch() changes. I am happy to
> have a go at this, but first I need a clear statement from whoever
> maintains that area that keeping memory nodes *just* for the
> annotations (and otherwise ignore them) is the way forward (Rob?
> Grant?)
Wasn't there the approach to check for consistency between efi tables
and devicetree? Thus, DT is actually not ignored but rather checked if
it is in sync with efi tables.
-Robert
next prev parent reply other threads:[~2016-02-20 10:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 1:13 [PATCH v11 00/10] arm64, numa: Add numa support for arm64 platforms David Daney
2016-02-20 1:13 ` [PATCH v11 01/10] of/fdt: make generic early_init_dt_add_memory_arch() a weak alias David Daney
2016-02-20 1:13 ` [PATCH v11 02/10] arm64: override generic version of early_init_dt_add_memory_arch() David Daney
2016-02-20 1:13 ` [PATCH v11 03/10] efi: move FDT handling to separate object file David Daney
2016-02-20 1:13 ` [PATCH v11 04/10] arm64/efi: move EFI /chosen node parsing before early FDT processing David Daney
2016-02-20 1:13 ` [PATCH v11 05/10] arm64/efi: ignore DT memory nodes instead of removing them David Daney
2016-02-20 1:13 ` [PATCH v11 06/10] arm64/efi: ignore DT memreserve entries " David Daney
2016-02-20 1:13 ` [PATCH v11 07/10] Documentation, dt, numa: dt bindings for NUMA David Daney
2016-02-20 1:13 ` [PATCH v11 08/10] dt, numa: Add NUMA dt binding implementation David Daney
2016-02-23 19:36 ` Rob Herring
2016-02-26 1:26 ` David Daney
2016-02-26 18:27 ` Will Deacon
2016-03-01 16:56 ` Rob Herring
2016-03-01 16:47 ` Rob Herring
2016-03-01 16:57 ` David Daney
2016-03-01 17:43 ` Rob Herring
2016-03-01 17:58 ` David Daney
2016-02-20 1:13 ` [PATCH v11 09/10] arm64, numa: Add NUMA support for arm64 platforms David Daney
2016-02-20 1:13 ` [PATCH v11 10/10] arm64, mm, numa: Add NUMA balancing support for arm64 David Daney
2016-02-20 8:20 ` [PATCH v11 00/10] arm64, numa: Add numa support for arm64 platforms Ard Biesheuvel
2016-02-20 10:39 ` Robert Richter [this message]
2016-02-20 10:44 ` Ard Biesheuvel
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=20160220103959.GC4914@rric.localdomain \
--to=robert.richter@caviumnetworks.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