From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Michael Ellerman Subject: Re: Kconfig label updates In-Reply-To: <20190111112024.GD14180@gate.crashing.org> References: <20190108223024.GA147017@google.com> <87tviiroqy.fsf@concordia.ellerman.id.au> <83241c8b-8f44-162b-b42a-0f4f9bb858e7@linux.vnet.ibm.com> <874lafg23v.fsf@concordia.ellerman.id.au> <20190111112024.GD14180@gate.crashing.org> Date: Mon, 14 Jan 2019 21:42:48 +1100 Message-ID: <87muo3zfiv.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-pci-owner@vger.kernel.org List-Archive: List-Post: To: Segher Boessenkool Cc: Tyrel Datwyler , Bjorn Helgaas , linux-s390@vger.kernel.org, Heiko Carstens , linux-kernel@vger.kernel.org, Paul Mackerras , linux-pci@vger.kernel.org, Martin Schwidefsky , linuxppc-dev@lists.ozlabs.org List-ID: Segher Boessenkool writes: > On Fri, Jan 11, 2019 at 05:06:12PM +1100, Michael Ellerman wrote: >> Tyrel Datwyler writes: >> > It is basically the predecessor to PAPR "Power Architecture Platform Reference". >> > Which the LoPAPR document is available through power.org. Not sure if there is >> > any desire to adopt PAPR in place of RPA. It is the platform reference doc that >> > outlines how we do DLPAR and PCI Hotplug. >> >> True. But a user is unlikely to know "PAPR" either, and it googles badly. > > Googling for "powerpc papr" works fine afais? With a working link to a > pdf on the first page and all! True if you know to add "powerpc". I only get a link to LoPAPR, which is similar but not identical. If there's a link to PAPR then someone is in trouble :) cheers