From mboxrd@z Thu Jan 1 00:00:00 1970 From: Reza Arbab Subject: Re: [PATCH v6 4/4] of/fdt: mark hotpluggable memory Date: Mon, 14 Nov 2016 13:34:52 -0600 Message-ID: <20161114193451.bzowsi6csesoxwap@arbab-laptop.austin.ibm.com> References: <1478562276-25539-1-git-send-email-arbab@linux.vnet.ibm.com> <1478562276-25539-5-git-send-email-arbab@linux.vnet.ibm.com> <87bmxii85s.fsf@concordia.ellerman.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Return-path: Content-Disposition: inline In-Reply-To: <87bmxii85s.fsf@concordia.ellerman.id.au> Sender: owner-linux-mm@kvack.org To: Michael Ellerman Cc: Benjamin Herrenschmidt , Paul Mackerras , Andrew Morton , Rob Herring , Frank Rowand , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org, devicetree@vger.kernel.org, Bharata B Rao , Nathan Fontenot , Stewart Smith , Alistair Popple , Balbir Singh , "Aneesh Kumar K.V" , linux-kernel@vger.kernel.org List-Id: devicetree@vger.kernel.org On Mon, Nov 14, 2016 at 10:59:43PM +1100, Michael Ellerman wrote: >So I'm not opposed to this, but it is a little vague. > >What does the "hotpluggable" property really mean? > >Is it just a hint to the operating system? (which may or may not be >Linux). > >Or is it a direction, "this memory must be able to be hotunplugged"? > >I think you're intending the former, ie. a hint, which is probably OK. >But it needs to be documented clearly. Yes, you've got it right. It's just a hint, not a mandate. I'm about to send v7 which adds a description of "hotpluggable" in the documentation. Hopefully I've explained it well enough there. -- Reza Arbab -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org