Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp680719imu; Wed, 9 Jan 2019 04:44:15 -0800 (PST) X-Google-Smtp-Source: ALg8bN7H1XpaxH7tkk4eksLFoUyn0aGebxknuB6LGJzihU6p87oa1WxVj1JOK3IDScWR1Dkp8/MN X-Received: by 2002:a17:902:45:: with SMTP id 63mr5675457pla.272.1547037855876; Wed, 09 Jan 2019 04:44:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547037855; cv=none; d=google.com; s=arc-20160816; b=KO4ib2bnTVZX1EZQFZJpgIygbSzwrSLR03A0hROCCIXKWJEp9OYkduMtNncjpkoHho 4M+jpiGceQkPHBSZ/07WkmDHvAuGcvkEi+tX5lVhTEX0iDqFlmp3VMLCA+TsFdb4hWef J31CdHCcAcGKjDbgiGevvNUHYSwNty6jZ61t47mFQEDLuGZD/JT1GDO0Yqb72jceW6BQ 8CGTtzwf2KwFyOOMfZJFsdsNpHmQQ46yexYTodm+qra2WwBhG27Y4SkYxKlOnqdGMvYS Gb7dhAvPE6GP/I0mvTXaixGk5xeBAQN9wu3eJKeH7vvMjaIVBYIA9DDztygSZ+AVtw3V tpMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=JKlPy9mR0NsiBOhQoyB8GT/8lh9+ytR3a9PLxWQNVVM=; b=ghoYBqyZDNMW7N2lZlO6XGKOuzDOBELUxjSsyvQ2EBsARS+M7Qig8+H8JxUlBD+IhA IN+ZDr631j669Ek32AKQZqlO07oVggiZd3e9zpJyTc3ZpbSfamjy8VKLfgLsuIT4Hyt7 zwvPZRW6PPa5DcNRc7BtCcdcvCWx/Blh/XlKUsoAAEqmDcwhjew/dY9HnnLkjc7pHSpS n6v6DC/qlVwKf4bycRqKZmijehpWfJMgh2m3/wAZ6UR3flMRJIiRKTPxXSccrVxGIiTz NcDEHNOROlqhAAShM4Q5FjnY/kMACoPjWyZ7XFy0meHVRQdoZrDEcvhvbCtfwzvQ8v1K +puA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b21si46523687pfb.89.2019.01.09.04.44.00; Wed, 09 Jan 2019 04:44:15 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730543AbfAIMhR (ORCPT + 99 others); Wed, 9 Jan 2019 07:37:17 -0500 Received: from ozlabs.org ([203.11.71.1]:50549 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730438AbfAIMhR (ORCPT ); Wed, 9 Jan 2019 07:37:17 -0500 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPSA id 43ZTCs0zQVz9sDL; Wed, 9 Jan 2019 23:37:13 +1100 (AEDT) From: Michael Ellerman To: Bjorn Helgaas , Tyrel Datwyler Cc: Benjamin Herrenschmidt , Paul Mackerras , 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: Re: Kconfig label updates In-Reply-To: <20190108223024.GA147017@google.com> References: <20190108223024.GA147017@google.com> Date: Wed, 09 Jan 2019 23:37:09 +1100 Message-ID: <87tviiroqy.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Bjorn, Bjorn Helgaas writes: > 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. Yeah I think just remove it, it's not a well known term and is unlikely to help anyone these days. It stands for "RISC Platform Architecture", which was some kind of specification for Power machines back in the day, but from what I can tell it was never used in marketing or manuals much (hence so few hits on Google). > 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? No I don't think so. > 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" TBH these are pretty unhelpful too. PowerNV is not a marketing name and so doesn't appear anywhere much in official manuals or brochures and it's also used on non-IBM branded machines. And pSeries & iSeries were marketing names but are no longer used. We should probably update that text, but we can do that later, rather than blocking this patch. > 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" This is used in non-IBM machines as well. So perhaps: ? tristate "IBM/OpenPower PowerNV (bare metal) PCI Hotplug driver" > @@ -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" I think just drop RPA here. > depends on PPC_PSERIES && EEH > help > Say Y here if you have a RPA system that supports PCI Hotplug. s/RPA/IBM Power Systems/ > + This includes the earlier pSeries and iSeries. To be complete: This includes the earlier System p, System i, 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" Again just drop RPA. cheers