From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH v2 5/8] mm/memory_hotplug: Drop MHP_MEMBLOCK_API References: <20190507183804.5512-1-david@redhat.com> <20190507183804.5512-6-david@redhat.com> <1557356938.3028.35.camel@suse.com> From: David Hildenbrand Message-ID: Date: Thu, 9 May 2019 09:05:23 +0200 MIME-Version: 1.0 In-Reply-To: <1557356938.3028.35.camel@suse.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-Archive: List-Post: To: osalvador , Dan Williams Cc: Linux MM , Linux Kernel Mailing List , linux-ia64@vger.kernel.org, linuxppc-dev , linux-s390 , Linux-sh , Andrew Morton , Michal Hocko , Pavel Tatashin , Wei Yang , Joonsoo Kim , Qian Cai , Arun KS , Mathieu Malaterre List-ID: On 09.05.19 01:08, osalvador wrote: > On Wed, 2019-05-08 at 09:39 +0200, David Hildenbrand wrote: >> However I haven't really thought it through yet, smalles like that >> could >> as well just be handled by the caller of >> arch_add_memory()/arch_remove_memory() eventually, passing it via >> something like the altmap parameter. >> >> Let's leave it in place for now, we can talk about that once we have >> new >> patches from Oscar. > Hi David, > > I plan to send a new patchset once this is and Dan's are merged, > otherwise I will have a mayhem with the conflicts. > > I also plan/want to review this patchset, but time is tight this week. > Sure, take your time. I'll resend this patch set most probably tomorrow or early next week. Cheers! -- Thanks, David / dhildenb