Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   osalvador@techadventures.net
To:     linux-mm@kvack.org
Cc:     pasha.tatashin@oracle.com, mhocko@suse.com, vbabka@suse.cz,
        akpm@linux-foundation.org, aaron.lu@intel.com,
        iamjoonsoo.kim@lge.com, linux-kernel@vger.kernel.org,
        Oscar Salvador <osalvador@suse.de>
Subject: [RFC PATCH 0/3] Cleanup for free_area_init_node / free_area_init_core
Date:   Tue, 17 Jul 2018 12:56:19 +0200
Message-Id: <20180717105622.12410-1-osalvador@techadventures.net>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Oscar Salvador <osalvador@suse.de>

While trying to cleanup the memhotplug code, I found quite difficult to follow
free_area_init_node / free_area_init_core wrt which functions get called
from the memhotplug path.

This is en effort to try to refactor / cleanup those two functions a little bit,
to make them easier to read.

It compiles, but I did not test it.
I would like to get some feedback to see if it is worth or not. 

Signed-off-by: Oscar Salvador <osalvador@suse.de>

Oscar Salvador (3):
  mm: Make free_area_init_core more readable by moving the ifdefs
  mm: Refactor free_area_init_core
  mm: Make free_area_init_node call certain functions only when booting

 mm/page_alloc.c | 193 ++++++++++++++++++++++++++++++++++----------------------
 1 file changed, 116 insertions(+), 77 deletions(-)

-- 
2.13.6