From: Michal Hocko <mhocko@suse.com>
To: Laurent Dufour <ldufour@linux.ibm.com>
Cc: akpm@linux-foundation.org, David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-mm@kvack.org, "Rafael J . Wysocki" <rafael@kernel.org>,
nathanl@linux.ibm.com, cheloha@linux.ibm.com,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mm: replace memmap_context by memplug_context
Date: Mon, 14 Sep 2020 10:59:53 +0200 [thread overview]
Message-ID: <20200914085953.GD16999@dhcp22.suse.cz> (raw)
In-Reply-To: <d3843235-2e02-a4ad-494c-20222a7e3b45@linux.ibm.com>
On Mon 14-09-20 10:51:06, Laurent Dufour wrote:
> Le 14/09/2020 à 10:49, Michal Hocko a écrit :
[...]
> > /*
> > * Memory initialization context, use to differentiate memory added by
> > * the platform statically or via memory hotplug interface.
> > */
> > enum meminit_context {
> > MEMINIT_EARLY,
> > MEMINIT_HOTPLUG
> > }
> >
>
> Sounds good too.
> What about its definition's place, in include/mm/zone.h as David suggested ?
Yes. This shouldn't be in the hotplug proper.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-09-14 9:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 13:48 mm: fix memory to node bad links in sysfs Laurent Dufour
2020-09-11 13:48 ` [PATCH 1/3] mm: replace memmap_context by memplug_context Laurent Dufour
2020-09-11 14:59 ` David Hildenbrand
2020-09-11 16:23 ` Laurent Dufour
2020-09-11 17:34 ` David Hildenbrand
2020-09-14 8:49 ` Michal Hocko
2020-09-14 8:51 ` Laurent Dufour
2020-09-14 8:59 ` Michal Hocko [this message]
2020-09-11 13:48 ` [PATCH 2/3] mm: don't rely on system state to detect hot-plug operations Laurent Dufour
2020-09-14 7:57 ` David Hildenbrand
2020-09-14 8:05 ` Laurent Dufour
2020-09-14 8:19 ` Oscar Salvador
2020-09-14 8:31 ` David Hildenbrand
2020-09-14 9:16 ` Laurent Dufour
2020-09-14 9:19 ` David Hildenbrand
2020-09-14 8:39 ` Laurent Dufour
2020-09-14 8:55 ` Michal Hocko
2020-09-11 13:48 ` [PATCH 3/3] mm: don't panic when links can't be created in sysfs Laurent Dufour
2020-09-11 14:01 ` Greg Kroah-Hartman
2020-09-11 16:27 ` Laurent Dufour
2020-09-14 8:59 ` Michal Hocko
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=20200914085953.GD16999@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cheloha@linux.ibm.com \
--cc=david@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ldufour@linux.ibm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nathanl@linux.ibm.com \
--cc=osalvador@suse.de \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.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