From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mm, numa: boot cpu should bound to the node0 when node_off enable
Date: Tue, 23 Aug 2016 12:30:54 +0100 [thread overview]
Message-ID: <20160823113054.GC28945@arm.com> (raw)
In-Reply-To: <57BC3125.7090003@huawei.com>
On Tue, Aug 23, 2016 at 07:19:01PM +0800, Leizhen (ThunderTown) wrote:
> He applied my patches, which I mentioned these days.
[...]
> I will update my patch series and resend it again.
To be clear, you plan to send an updated version of:
[PATCH v6 00/14] fix some type infos and bugs for arm64/of numa
so I can ignore v6 of that?
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
zhong jiang <zhongjiang@huawei.com>,
Mark Rutland <mark.rutland@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Ganapatrao Kulkarni <gpkulkarni@gmail.com>
Subject: Re: [PATCH] mm, numa: boot cpu should bound to the node0 when node_off enable
Date: Tue, 23 Aug 2016 12:30:54 +0100 [thread overview]
Message-ID: <20160823113054.GC28945@arm.com> (raw)
In-Reply-To: <57BC3125.7090003@huawei.com>
On Tue, Aug 23, 2016 at 07:19:01PM +0800, Leizhen (ThunderTown) wrote:
> He applied my patches, which I mentioned these days.
[...]
> I will update my patch series and resend it again.
To be clear, you plan to send an updated version of:
[PATCH v6 00/14] fix some type infos and bugs for arm64/of numa
so I can ignore v6 of that?
Will
next prev parent reply other threads:[~2016-08-23 11:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 13:09 [PATCH] mm, numa: boot cpu should bound to the node0 when node_off enable zhongjiang
2016-08-18 13:09 ` [PATCH] mm,numa: " zhongjiang
2016-08-18 16:04 ` [PATCH] mm, numa: " Catalin Marinas
2016-08-18 16:04 ` Catalin Marinas
2016-08-18 17:45 ` Ganapatrao Kulkarni
2016-08-18 17:45 ` Ganapatrao Kulkarni
2016-08-19 1:41 ` zhong jiang
2016-08-19 1:41 ` zhong jiang
2016-08-19 1:58 ` zhong jiang
2016-08-19 1:58 ` zhong jiang
2016-08-19 4:00 ` Ganapatrao Kulkarni
2016-08-19 4:00 ` Ganapatrao Kulkarni
2016-08-19 4:11 ` Ganapatrao Kulkarni
2016-08-19 4:11 ` Ganapatrao Kulkarni
2016-08-20 9:38 ` zhong jiang
2016-08-20 9:38 ` zhong jiang
2016-08-22 14:28 ` Catalin Marinas
2016-08-22 14:28 ` Catalin Marinas
2016-08-23 7:47 ` zhong jiang
2016-08-23 7:47 ` zhong jiang
2016-08-23 7:54 ` Leizhen (ThunderTown)
2016-08-23 11:19 ` Leizhen (ThunderTown)
2016-08-23 11:19 ` Leizhen (ThunderTown)
2016-08-23 11:30 ` Will Deacon [this message]
2016-08-23 11:30 ` Will Deacon
2016-08-23 11:50 ` Leizhen (ThunderTown)
2016-08-23 11:50 ` Leizhen (ThunderTown)
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=20160823113054.GC28945@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.