From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Oscar Salvador <OSalvador@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
Wen Congyang <tangchen@cn.fujitsu.com>,
Tang Chen <wency@cn.fujitsu.com>, Miroslav Benes <mbenes@suse.cz>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [RFC PATCH] mm, memory_hotplug: do not clear numa_node association after hot_remove
Date: Thu, 15 Nov 2018 08:34:57 +0100 [thread overview]
Message-ID: <20181115073457.GB23831@dhcp22.suse.cz> (raw)
In-Reply-To: <20181114151809.06c43a508cc773d3a5ee04f4@linux-foundation.org>
On Wed 14-11-18 15:18:09, Andrew Morton wrote:
> On Wed, 14 Nov 2018 08:14:42 +0100 Michal Hocko <mhocko@kernel.org> wrote:
>
> > It seems there were no objections here. So can we have it in linux-next
> > for a wider testing a possibly target the next merge window?
> >
>
> top-posting sucks!
I thought it would make your life easier in this case. Will do it
differently next time.
> I already have this queued for 4.21-rc1.
Thanks! I must have missed the mm-commit email.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2018-11-15 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 10:04 [RFC PATCH] mm, memory_hotplug: do not clear numa_node association after hot_remove Michal Hocko
2018-11-08 10:29 ` Michal Hocko
2018-11-09 3:42 ` Anshuman Khandual
2018-11-09 7:59 ` Michal Hocko
2018-11-09 11:04 ` Anshuman Khandual
2018-11-09 11:07 ` Michal Hocko
2018-12-20 22:48 ` Andrew Morton
2018-11-14 7:14 ` Michal Hocko
2018-11-14 23:18 ` Andrew Morton
2018-11-15 7:34 ` Michal Hocko [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=20181115073457.GB23831@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=OSalvador@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbenes@suse.cz \
--cc=tangchen@cn.fujitsu.com \
--cc=vbabka@suse.cz \
--cc=wency@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).