From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH V3 0/3] mm/memory_hotplug: Pre-validate the address range with platform References: <1610975582-12646-1-git-send-email-anshuman.khandual@arm.com> <20210119134016.GA23408@linux> From: Anshuman Khandual Message-ID: <8df4e1e1-1ddd-398e-c9a6-17a67d8a95bc@arm.com> Date: Wed, 20 Jan 2021 14:07:18 +0530 MIME-Version: 1.0 In-Reply-To: <20210119134016.GA23408@linux> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-ID: To: Oscar Salvador , David Hildenbrand Cc: linux-mm@kvack.org, akpm@linux-foundation.org, hca@linux.ibm.com, catalin.marinas@arm.com, Vasily Gorbik , Will Deacon , Ard Biesheuvel , Mark Rutland , linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org On 1/19/21 7:10 PM, Oscar Salvador wrote: > On Tue, Jan 19, 2021 at 02:33:03PM +0100, David Hildenbrand wrote: >> Minor thing, we should make up our mind if we want to call stuff >> internally "memhp_" or "mhp". I prefer the latter, because it is shorter. > > I would rather use the latter as well. I used that in [1]. Okay, will change all that is 'memhp' as 'mhp' instead. > MEMHP_MERGE_RESOURCE should be renamed if we agree on that. > > [1] https://patchwork.kernel.org/project/linux-mm/cover/20201217130758.11565-1-osalvador@suse.de/ > >