Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp77065imu; Tue, 8 Jan 2019 15:01:57 -0800 (PST) X-Google-Smtp-Source: ALg8bN7oeUI99CS3VEXJpOhxsxmga2fSDINQP0L0eNe2IhUqTacfJsAK17x8VCFQlRU00SIojKIp X-Received: by 2002:a62:220d:: with SMTP id i13mr3583264pfi.162.1546988517128; Tue, 08 Jan 2019 15:01:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546988517; cv=none; d=google.com; s=arc-20160816; b=L8TWjxFKvTfQrxyUaUtf1ob/miSna+7R8YfNwwdPGoSytQUVcSStCIlU+3bh6OFv/G 9QvSfm3pZ77kJO6oYdwMHih0Nh0HgcsiOU+/5CvrO6uED3wi7EnIcNOLT7hIkEnh7Shx DnoGiieV1lcntxDIHFEyDPc2jiA/4nnHiGgWc3QJPpN9r3f/EjsFxNFWLTF/5TGLYxoY RKkGJUWnCgGBEyNIn+0hEItkDPlTYiohs1Wcqs90pGnLWoafyGsgcMuS5vMcG3ybQRl/ vogVvZQRQmfgJklPzh1BvWJfuOBFzaRW2RnDUx/9iPbfTnnH8S6I6EjlTGiXbiQVCTGg 0Rrg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:cc:to:from:date:dkim-signature; bh=NrPWHqI3lkSOBkREv60RGuZ6fcghGepa4KbrMKW2LiE=; b=UXczPmi7C4pf7Ppo6v2ZpBKZpQBts18rbC3qobQ9uzfP+2rDsjR1Yx8HgqpjwRD8Fi 6POleYi/8Zc3nsHWQxOjrVebNEu/Rhpg610gU3+jKMh4xQBbIls1EdAO1gDmqJXJ12BM ugH+HUuXJTii0lONsdxMp/jqrmRUE5xs+BxRJz632Tm7QlBgx/qyy/aGLYrcn67rf0pJ mExGHZ86aFd6VH8lSQp7SuxyCAaM95fgEeXhbPoBZ4Gq0ozMzhB5nnKyLoscPs6HukWO +1S6xHPcjRH7ZqnUKmb/7whNWQ7qnlcRuDbzB6Yvy7Eroas+nJyeJZOkr1M3xDkF+uAr wvLw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=d0tFW0jR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v16si12119465pgc.519.2019.01.08.15.01.34; Tue, 08 Jan 2019 15:01:57 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=d0tFW0jR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729674AbfAHWa3 (ORCPT + 99 others); Tue, 8 Jan 2019 17:30:29 -0500 Received: from mail.kernel.org ([198.145.29.99]:37238 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729042AbfAHWa2 (ORCPT ); Tue, 8 Jan 2019 17:30:28 -0500 Received: from localhost (unknown [69.71.4.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5171A20665; Tue, 8 Jan 2019 22:30:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1546986627; bh=hXnMppBc3pgIEOn2BXm63YNiYbwzeHEpcsiQ/uzH2Vo=; h=Date:From:To:Cc:Subject:From; b=d0tFW0jR/zJ+oALZ7m+kmx7JDFbj56gT9DSOEyAOFtVIgHdRbs6E623oevDaD3oPV WkylKhjBM6wLu3nfjjb8r6wTPvVn5vX8AKIPBPKMtBj0lUFYH0Xf78VcSTJuEQLL0q T9uepaluzZlPF4O20miGOQvdPlplfzrYtmseR34s= Date: Tue, 8 Jan 2019 16:30:24 -0600 From: Bjorn Helgaas To: Tyrel Datwyler Cc: Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Martin Schwidefsky , Heiko Carstens , linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Kconfig label updates Message-ID: <20190108223024.GA147017@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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