From: David Daney <ddaney@caviumnetworks.com>
To: Jon Masters <jcm@redhat.com>
Cc: Will Deacon <will.deacon@arm.com>,
<linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>,
Robert Richter <rrichter@cavium.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Matt Fleming <matt@codeblueprint.co.uk>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
<linux-efi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH v15 0/6] arm64, numa: Add numa support for arm64 platforms
Date: Tue, 22 Mar 2016 14:45:57 -0700 [thread overview]
Message-ID: <56F1BD15.4000701@caviumnetworks.com> (raw)
In-Reply-To: <56F1936E.1090407@redhat.com>
On 03/22/2016 11:48 AM, Jon Masters wrote:
> On 03/08/2016 06:59 PM, David Daney wrote:
>
>> From: David Daney <david.daney@cavium.com>
>>
>> v15:
>>
>> - Make the distance-map node optional (again), if it is not in
>> the device tree, default values are used.
>>
>> - Minor cleanups to of_numa.c as suggested by Rob Harring.
>
> Hi David, all,
>
> Wondering what the status of this patch series is currently?
I haven't seen any feedback on v15. My assumption was that the relevant
arm64 maintainers would take some sort of action after the merge window
quiets down.
In any event, I am happy to make any improvements that may be suggested.
David Daney
next prev parent reply other threads:[~2016-03-22 21:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 23:59 [PATCH v15 0/6] arm64, numa: Add numa support for arm64 platforms David Daney
2016-03-08 23:59 ` [PATCH v15 1/6] efi: ARM/arm64: ignore DT memory nodes instead of removing them David Daney
2016-03-18 12:26 ` Matt Fleming
2016-03-18 12:31 ` Ard Biesheuvel
2016-03-18 12:56 ` Matt Fleming
2016-03-18 13:11 ` Ard Biesheuvel
2016-03-08 23:59 ` [PATCH v15 2/6] Documentation, dt, numa: dt bindings for NUMA David Daney
2016-03-08 23:59 ` [PATCH v15 3/6] of, numa: Add NUMA of binding implementation David Daney
2016-03-08 23:59 ` [PATCH v15 4/6] arm64: Move unflatten_device_tree() call earlier David Daney
2016-03-08 23:59 ` [PATCH v15 5/6] arm64, numa: Add NUMA support for arm64 platforms David Daney
2016-04-13 14:09 ` Steve Capper
2016-04-13 14:30 ` Steve Capper
2016-03-08 23:59 ` [PATCH v15 6/6] arm64, mm, numa: Add NUMA balancing support for arm64 David Daney
2016-03-22 18:48 ` [PATCH v15 0/6] arm64, numa: Add numa support for arm64 platforms Jon Masters
2016-03-22 21:45 ` David Daney [this message]
2016-04-05 13:08 ` Graeme Gregory
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=56F1BD15.4000701@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=david.daney@cavium.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=galak@codeaurora.org \
--cc=gkulkarni@caviumnetworks.com \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matt@codeblueprint.co.uk \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rrichter@cavium.com \
--cc=will.deacon@arm.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