From: zhong jiang <zhongjiang@huawei.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
lenb@kernel.org, akpm@linux-foundation.org, vbabka@suse.cz,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Ingo Molnar <mingo@kernel.org>, Minchan Kim <minchan@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
"mgorman@techsingularity.net" <mgorman@techsingularity.net>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
richard.weiyang@gmail.com, pombredanne@nexb.com,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] x86/numa: move setting parse numa node to num_add_memblk
Date: Fri, 1 Dec 2017 17:01:54 +0800 [thread overview]
Message-ID: <5A211A82.1090808@huawei.com> (raw)
In-Reply-To: <20171201085833.4hs6sgjvcokdrr35@dhcp22.suse.cz>
On 2017/12/1 16:58, Michal Hocko wrote:
> On Fri 01-12-17 16:48:25, zhong jiang wrote:
>> +cc more mm maintainer.
>>
>> Any one has any object. please let me know.
> Please repost with the changelog which actually tells 1) what is the
> problem 2) why do we need to address it and 3) how do we address it.
Fine, I will repost later.
Thanks
zhong jiang
WARNING: multiple messages have this Message-ID (diff)
From: zhong jiang <zhongjiang@huawei.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <x86@kernel.org>,
<lenb@kernel.org>, <akpm@linux-foundation.org>, <vbabka@suse.cz>,
<linux-mm@kvack.org>, David Rientjes <rientjes@google.com>,
Ingo Molnar <mingo@kernel.org>, Minchan Kim <minchan@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
"mgorman@techsingularity.net" <mgorman@techsingularity.net>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>, <richard.weiyang@gmail.com>,
<pombredanne@nexb.com>, <linux-kernel@vger.kernel.org>,
<linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] x86/numa: move setting parse numa node to num_add_memblk
Date: Fri, 1 Dec 2017 17:01:54 +0800 [thread overview]
Message-ID: <5A211A82.1090808@huawei.com> (raw)
In-Reply-To: <20171201085833.4hs6sgjvcokdrr35@dhcp22.suse.cz>
On 2017/12/1 16:58, Michal Hocko wrote:
> On Fri 01-12-17 16:48:25, zhong jiang wrote:
>> +cc more mm maintainer.
>>
>> Any one has any object. please let me know.
> Please repost with the changelog which actually tells 1) what is the
> problem 2) why do we need to address it and 3) how do we address it.
Fine, I will repost later.
Thanks
zhong jiang
WARNING: multiple messages have this Message-ID (diff)
From: zhong jiang <zhongjiang@huawei.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
lenb@kernel.org, akpm@linux-foundation.org, vbabka@suse.cz,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Ingo Molnar <mingo@kernel.org>, Minchan Kim <minchan@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
"mgorman@techsingularity.net" <mgorman@techsingularity.net>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
richard.weiyang@gmail.com, pombredanne@nexb.com,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] x86/numa: move setting parse numa node to num_add_memblk
Date: Fri, 1 Dec 2017 17:01:54 +0800 [thread overview]
Message-ID: <5A211A82.1090808@huawei.com> (raw)
In-Reply-To: <20171201085833.4hs6sgjvcokdrr35@dhcp22.suse.cz>
On 2017/12/1 16:58, Michal Hocko wrote:
> On Fri 01-12-17 16:48:25, zhong jiang wrote:
>> +cc more mm maintainer.
>>
>> Any one has any object. please let me know.
> Please repost with the changelog which actually tells 1) what is the
> problem 2) why do we need to address it and 3) how do we address it.
Fine, I will repost later.
Thanks
zhong jiang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-01 9:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 9:13 [PATCH] x86/numa: move setting parse numa node to num_add_memblk zhong jiang
2017-11-29 9:13 ` zhong jiang
2017-11-29 9:13 ` zhong jiang
2017-11-29 12:03 ` Michal Hocko
2017-11-29 12:03 ` Michal Hocko
2017-11-29 12:41 ` zhong jiang
2017-11-29 12:41 ` zhong jiang
2017-11-29 12:41 ` zhong jiang
2017-11-29 13:01 ` Michal Hocko
2017-11-29 13:01 ` Michal Hocko
2017-11-29 13:26 ` zhong jiang
2017-11-29 13:26 ` zhong jiang
2017-11-29 13:33 ` Michal Hocko
2017-11-29 13:33 ` Michal Hocko
2017-11-29 13:44 ` zhong jiang
2017-11-29 13:44 ` zhong jiang
2017-11-29 14:14 ` Dou Liyang
2017-11-29 14:14 ` Dou Liyang
2017-11-30 4:39 ` zhong jiang
2017-11-30 4:39 ` zhong jiang
2017-12-01 8:48 ` zhong jiang
2017-12-01 8:48 ` zhong jiang
2017-12-01 8:48 ` zhong jiang
2017-12-01 8:58 ` Michal Hocko
2017-12-01 8:58 ` Michal Hocko
2017-12-01 9:01 ` zhong jiang [this message]
2017-12-01 9:01 ` zhong jiang
2017-12-01 9:01 ` zhong jiang
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=5A211A82.1090808@huawei.com \
--to=zhongjiang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pombredanne@nexb.com \
--cc=richard.weiyang@gmail.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=x86@kernel.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.