From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v4 0/4] arm64:numa: Add numa support for arm64 platforms.
Date: Tue, 30 Jun 2015 15:01:23 +0100 [thread overview]
Message-ID: <20150630140123.GL27725@arm.com> (raw)
In-Reply-To: <CAFpQJXXZc0sop601wrmTe5Ng0SiSGfT9AA2Dpf=X9bgGN9srrA@mail.gmail.com>
On Mon, Jun 29, 2015 at 11:57:49AM +0100, Ganapatrao Kulkarni wrote:
> Hi Catalin, Will, Mark,
>
> can you please have a look of numa patches and share your review comments.
Nothing has changed since the last time you poked me about this series:
- There are open comments from Hanjun
- The device-tree part hasn't been reviewed by a DT maintainer
so I can't merge anything other than the Kconfig change atm.
Will
next prev parent reply other threads:[~2015-06-30 14:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 11:05 [RFC PATCH v4 0/4] arm64:numa: Add numa support for arm64 platforms Ganapatrao Kulkarni
2015-01-22 11:05 ` [RFC PATCH v4 1/4] arm64: defconfig: increase NR_CPUS range to 2-4096 Ganapatrao Kulkarni
2015-01-22 11:05 ` [RFC PATCH v4 2/4] Documentation: arm64/arm: dt bindings for numa Ganapatrao Kulkarni
2015-01-22 11:05 ` [RFC PATCH v4 3/4] arm64:thunder: Add initial dts for Cavium's Thunder SoC in 2 Node topology Ganapatrao Kulkarni
2015-01-22 16:47 ` Arnd Bergmann
2015-01-22 18:26 ` Arnd Bergmann
2015-01-23 12:37 ` Ganapatrao Kulkarni
2015-02-24 8:52 ` Ganapatrao Kulkarni
2015-03-10 8:42 ` Ganapatrao Kulkarni
2015-03-18 4:02 ` Ganapatrao Kulkarni
2015-03-18 10:00 ` Will Deacon
2015-03-18 10:39 ` Ganapatrao Kulkarni
2015-03-18 10:47 ` Will Deacon
2015-01-22 11:05 ` [RFC PATCH v4 4/4] arm64:numa: adding numa support for arm64 platforms Ganapatrao Kulkarni
2015-02-27 9:08 ` Hanjun Guo
2015-06-29 10:57 ` [RFC PATCH v4 0/4] arm64:numa: Add " Ganapatrao Kulkarni
2015-06-30 14:01 ` Will Deacon [this message]
2015-06-30 14:22 ` Ganapatrao Kulkarni
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=20150630140123.GL27725@arm.com \
--to=will.deacon@arm.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).