From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
Bjorn Helgaas <helgaas@kernel.org>,
linux-s390@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
linux-pci@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Kconfig label updates
Date: Fri, 11 Jan 2019 05:20:24 -0600 [thread overview]
Message-ID: <20190111112024.GD14180@gate.crashing.org> (raw)
In-Reply-To: <874lafg23v.fsf@concordia.ellerman.id.au>
On Fri, Jan 11, 2019 at 05:06:12PM +1100, Michael Ellerman wrote:
> Tyrel Datwyler <tyreld@linux.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!
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-s390@vger.kernel.org, linux-pci@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Bjorn Helgaas <helgaas@kernel.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Kconfig label updates
Date: Fri, 11 Jan 2019 05:20:24 -0600 [thread overview]
Message-ID: <20190111112024.GD14180@gate.crashing.org> (raw)
In-Reply-To: <874lafg23v.fsf@concordia.ellerman.id.au>
On Fri, Jan 11, 2019 at 05:06:12PM +1100, Michael Ellerman wrote:
> Tyrel Datwyler <tyreld@linux.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!
Segher
next prev parent reply other threads:[~2019-01-11 11:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 22:30 Kconfig label updates Bjorn Helgaas
2019-01-08 22:30 ` Bjorn Helgaas
2019-01-09 1:00 ` Oliver
2019-01-09 1:00 ` Oliver
2019-01-09 8:35 ` Martin Schwidefsky
2019-01-09 8:35 ` Martin Schwidefsky
2019-01-09 12:37 ` Michael Ellerman
2019-01-09 12:37 ` Michael Ellerman
2019-01-10 20:37 ` Tyrel Datwyler
2019-01-10 20:37 ` Tyrel Datwyler
2019-01-11 6:06 ` Michael Ellerman
2019-01-11 6:06 ` Michael Ellerman
2019-01-11 11:20 ` Segher Boessenkool [this message]
2019-01-11 11:20 ` Segher Boessenkool
2019-01-14 10:42 ` Michael Ellerman
2019-01-14 10:42 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190111112024.GD14180@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=heiko.carstens@de.ibm.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=schwidefsky@de.ibm.com \
--cc=tyreld@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.