[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87muo3zfiv.fsf@concordia.ellerman.id.au>
Date: Mon, 14 Jan 2019 21:42:48 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Segher Boessenkool <segher@...nel.crashing.org>
Cc: Tyrel Datwyler <tyreld@...ux.vnet.ibm.com>,
Bjorn Helgaas <helgaas@...nel.org>, linux-s390@...r.kernel.org,
Heiko Carstens <heiko.carstens@...ibm.com>,
linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
linux-pci@...r.kernel.org,
Martin Schwidefsky <schwidefsky@...ibm.com>,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: Kconfig label updates
Segher Boessenkool <segher@...nel.crashing.org> writes:
> On Fri, Jan 11, 2019 at 05:06:12PM +1100, Michael Ellerman wrote:
>> Tyrel Datwyler <tyreld@...ux.vnet.ibm.com> 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
Powered by blists - more mailing lists