public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: Zhen Lei <thunder.leizhen@huawei.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	"Frank Rowand" <frowand.list@gmail.com>,
	devicetree <devicetree@vger.kernel.org>
Cc: Zefan Li <lizefan@huawei.com>, Xinwei Hu <huxinwei@huawei.com>,
	"Tianhong Ding" <dingtianhong@huawei.com>
Subject: Re: [PATCH v5 00/14] fix some type infos and bugs for arm64/of numa
Date: Wed, 10 Aug 2016 09:56:49 +0800	[thread overview]
Message-ID: <57AA89E1.6050103@huawei.com> (raw)
In-Reply-To: <1470647899-6324-1-git-send-email-thunder.leizhen@huawei.com>

Hi Zhen,

On 2016/8/8 17:18, Zhen Lei wrote:
> v4 -> v5:
> This version has no code changes, just add "Acked-by: Rob Herring <robh@kernel.org>"
> into patches 1, 2, 4, 6, 7, 13, 14. Because these patches rely on some acpi numa
> patches, and the latter had not been upstreamed in 4.7, but upstreamed in 4.8-rc1,
> so I resend my patches again.

I think we need to mention this patch set is rebased on top of 4,8-rc1, and

 - patch 1~5 are fixes which are targeting for 4.8.

 - patch 6~14 are cleanups and new features, which are targeting for 4.9, in detail,
   - patch 6~8 are cleanups
   - patch 9~14 are new features adding per cpu area and memory less node support.

Catalin, do you think Zhen needs to separate this patch set into two and then resend?

Thanks
Hanjun

      parent reply	other threads:[~2016-08-10  2:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08  9:18 [PATCH v5 00/14] fix some type infos and bugs for arm64/of numa Zhen Lei
2016-08-08  9:18 ` [PATCH v5 01/14] of/numa: remove a duplicated pr_debug information Zhen Lei
2016-08-08  9:18 ` [PATCH v5 02/14] of/numa: fix a memory@ node can only contains one memory block Zhen Lei
2016-08-08  9:18 ` [PATCH v5 03/14] arm64/numa: add nid check for " Zhen Lei
2016-08-10  2:12   ` Hanjun Guo
2016-08-10  3:42     ` Leizhen (ThunderTown)
2016-08-08  9:18 ` [PATCH v5 04/14] of/numa: remove a duplicated warning Zhen Lei
2016-08-08  9:18 ` [PATCH v5 05/14] arm64/numa: avoid inconsistent information to be printed Zhen Lei
2016-08-08  9:18 ` [PATCH v5 06/14] of_numa: Use of_get_next_parent to simplify code Zhen Lei
2016-08-08  9:18 ` [PATCH v5 07/14] of_numa: Use pr_fmt() Zhen Lei
2016-08-08  9:18 ` [PATCH v5 08/14] arm64: numa: " Zhen Lei
2016-08-08  9:18 ` [PATCH v5 09/14] arm64/numa: support HAVE_SETUP_PER_CPU_AREA Zhen Lei
2016-08-08  9:18 ` [PATCH v5 10/14] arm64/numa: define numa_distance as array to simplify code Zhen Lei
2016-08-08  9:18 ` [PATCH v5 11/14] arm64/numa: support HAVE_MEMORYLESS_NODES Zhen Lei
2016-08-08  9:18 ` [PATCH v5 12/14] arm64/numa: remove some useless code Zhen Lei
2016-08-08  9:18 ` [PATCH v5 13/14] of/numa: remove the constraint on the distances of node pairs Zhen Lei
2016-08-08  9:18 ` [PATCH v5 14/14] Documentation: " Zhen Lei
2016-08-10  1:56 ` Hanjun Guo [this message]

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=57AA89E1.6050103@huawei.com \
    --to=guohanjun@huawei.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dingtianhong@huawei.com \
    --cc=frowand.list@gmail.com \
    --cc=huxinwei@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=robh+dt@kernel.org \
    --cc=thunder.leizhen@huawei.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