From: Bjorn Helgaas <helgaas@kernel.org>
To: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Kconfig label updates
Date: Tue, 8 Jan 2019 16:30:24 -0600 [thread overview]
Message-ID: <20190108223024.GA147017@google.com> (raw)
Hi,
I want to update the PCI Kconfig labels so they're more consistent and
useful to users, something like the patch below. IIUC, the items
below are all IBM-related; please correct me if not.
I'd also like to expand (or remove) "RPA" because Google doesn't find
anything about "IBM RPA", except Robotic Process Automation, which I
think must be something else.
Is there some text expansion of RPA that we could use that would be
meaningful to a user, i.e., something he/she might find on a nameplate
or in a user manual?
Ideally the PCI Kconfig labels would match the terms used in
arch/.../Kconfig, e.g.,
config PPC_POWERNV
bool "IBM PowerNV (Non-Virtualized) platform support"
config PPC_PSERIES
bool "IBM pSeries & new (POWER5-based) iSeries"
config MARCH_Z900
bool "IBM zSeries model z800 and z900"
config MARCH_Z9_109
bool "IBM System z9"
Bjorn
diff --git a/drivers/pci/hotplug/Kconfig b/drivers/pci/hotplug/Kconfig
index e9f78eb390d2..1c1d145bfd84 100644
--- a/drivers/pci/hotplug/Kconfig
+++ b/drivers/pci/hotplug/Kconfig
@@ -112,7 +112,7 @@ config HOTPLUG_PCI_SHPC
When in doubt, say N.
config HOTPLUG_PCI_POWERNV
- tristate "PowerPC PowerNV PCI Hotplug driver"
+ tristate "IBM PowerNV PCI Hotplug driver"
depends on PPC_POWERNV && EEH
select OF_DYNAMIC
help
@@ -125,10 +125,11 @@ config HOTPLUG_PCI_POWERNV
When in doubt, say N.
config HOTPLUG_PCI_RPA
- tristate "RPA PCI Hotplug driver"
+ tristate "IBM Power Systems RPA PCI Hotplug driver"
depends on PPC_PSERIES && EEH
help
Say Y here if you have a RPA system that supports PCI Hotplug.
+ This includes the earlier pSeries and iSeries.
To compile this driver as a module, choose M here: the
module will be called rpaphp.
@@ -136,7 +137,7 @@ config HOTPLUG_PCI_RPA
When in doubt, say N.
config HOTPLUG_PCI_RPA_DLPAR
- tristate "RPA Dynamic Logical Partitioning for I/O slots"
+ tristate "IBM RPA Dynamic Logical Partitioning for I/O slots"
depends on HOTPLUG_PCI_RPA
help
Say Y here if your system supports Dynamic Logical Partitioning
@@ -157,7 +158,7 @@ config HOTPLUG_PCI_SGI
When in doubt, say N.
config HOTPLUG_PCI_S390
- bool "System z PCI Hotplug Support"
+ bool "IBM System z PCI Hotplug Support"
depends on S390 && 64BIT
help
Say Y here if you want to use the System z PCI Hotplug
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
Cc: 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: Kconfig label updates
Date: Tue, 8 Jan 2019 16:30:24 -0600 [thread overview]
Message-ID: <20190108223024.GA147017@google.com> (raw)
Hi,
I want to update the PCI Kconfig labels so they're more consistent and
useful to users, something like the patch below. IIUC, the items
below are all IBM-related; please correct me if not.
I'd also like to expand (or remove) "RPA" because Google doesn't find
anything about "IBM RPA", except Robotic Process Automation, which I
think must be something else.
Is there some text expansion of RPA that we could use that would be
meaningful to a user, i.e., something he/she might find on a nameplate
or in a user manual?
Ideally the PCI Kconfig labels would match the terms used in
arch/.../Kconfig, e.g.,
config PPC_POWERNV
bool "IBM PowerNV (Non-Virtualized) platform support"
config PPC_PSERIES
bool "IBM pSeries & new (POWER5-based) iSeries"
config MARCH_Z900
bool "IBM zSeries model z800 and z900"
config MARCH_Z9_109
bool "IBM System z9"
Bjorn
diff --git a/drivers/pci/hotplug/Kconfig b/drivers/pci/hotplug/Kconfig
index e9f78eb390d2..1c1d145bfd84 100644
--- a/drivers/pci/hotplug/Kconfig
+++ b/drivers/pci/hotplug/Kconfig
@@ -112,7 +112,7 @@ config HOTPLUG_PCI_SHPC
When in doubt, say N.
config HOTPLUG_PCI_POWERNV
- tristate "PowerPC PowerNV PCI Hotplug driver"
+ tristate "IBM PowerNV PCI Hotplug driver"
depends on PPC_POWERNV && EEH
select OF_DYNAMIC
help
@@ -125,10 +125,11 @@ config HOTPLUG_PCI_POWERNV
When in doubt, say N.
config HOTPLUG_PCI_RPA
- tristate "RPA PCI Hotplug driver"
+ tristate "IBM Power Systems RPA PCI Hotplug driver"
depends on PPC_PSERIES && EEH
help
Say Y here if you have a RPA system that supports PCI Hotplug.
+ This includes the earlier pSeries and iSeries.
To compile this driver as a module, choose M here: the
module will be called rpaphp.
@@ -136,7 +137,7 @@ config HOTPLUG_PCI_RPA
When in doubt, say N.
config HOTPLUG_PCI_RPA_DLPAR
- tristate "RPA Dynamic Logical Partitioning for I/O slots"
+ tristate "IBM RPA Dynamic Logical Partitioning for I/O slots"
depends on HOTPLUG_PCI_RPA
help
Say Y here if your system supports Dynamic Logical Partitioning
@@ -157,7 +158,7 @@ config HOTPLUG_PCI_SGI
When in doubt, say N.
config HOTPLUG_PCI_S390
- bool "System z PCI Hotplug Support"
+ bool "IBM System z PCI Hotplug Support"
depends on S390 && 64BIT
help
Say Y here if you want to use the System z PCI Hotplug
next reply other threads:[~2019-01-08 22:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 22:30 Bjorn Helgaas [this message]
2019-01-08 22:30 ` Kconfig label updates 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
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=20190108223024.GA147017@google.com \
--to=helgaas@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=heiko.carstens@de.ibm.com \
--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.