From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 925F4C43387 for ; Wed, 9 Jan 2019 01:01:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5048F2146F for ; Wed, 9 Jan 2019 01:01:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="OJdGXjxk" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728348AbfAIBBM (ORCPT ); Tue, 8 Jan 2019 20:01:12 -0500 Received: from mail-io1-f68.google.com ([209.85.166.68]:36588 "EHLO mail-io1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727829AbfAIBBM (ORCPT ); Tue, 8 Jan 2019 20:01:12 -0500 Received: by mail-io1-f68.google.com with SMTP id m19so4732035ioh.3; Tue, 08 Jan 2019 17:01:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GLBOEFW1BhFjPn/VvwGPbj8DpAhgGskTf+W4ne2TdMw=; b=OJdGXjxkhZTQtX4JfOQs2JCwWwI23LWlpkzbdXpAOovmlh9CPS6tj+yvlCEup40cJ+ 1xoOo/6wNgcr691iBTD3zxSm1JZrm62APL8Ot2Ta6kOWxDzvQcB/3YPl9e/pM9wYMbmV M9Rj0Qr3AJm6J3U/6BnqjQ2KP1vGYUpjLqZBKDnGS2onpV8NnO++j3D7VlYKynKMoITC 6mG3nO+6oQFJsznVPkntwcYhbs5n7TAuolxyWeBNhaKhLrbIKKrq/aJwZwyshRaj5qL0 e9xGFJsMF5YAsebFlEc1A1igqGxHJnYi0C9LIrNyAcEqmJIz74KHQ0iuzj9pis8zes5E LkOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GLBOEFW1BhFjPn/VvwGPbj8DpAhgGskTf+W4ne2TdMw=; b=rpUVX3z3z0WI2v6mk/dM4cPpNAwQeGdUoDyAcoKBnlkAXiMAankdt6Y+9Ijg06A81Z bghT8fvqjYoI9wCjcJOhtKkUQxqMBRMaAV5hcRkHu2MrrFgut9huXaeM6T3LTJo3PMVq 0dP6/ixzLC8CgBW7UXtdEsBUcgxgwC5zNIW/DOUPeBZbP1dyMiHd9ETvDVJ9Bwuud92S CFY8Mi9C5O7aAvRjTl3ZgxzGZaEo5oozeCHVEUmL8eZLDOR736sm9nEtX/V4PMfBphTg 7V+JcAnunx+YBEAgZidlja+VCDrKimaqyXjghrMv4rx78LBXNwDQxzhwz+79QxZq2VXD dK7g== X-Gm-Message-State: AJcUukdq3dEFxviKYvkKs5UFbKlhDFzu17tcsSIsquT4tRuCLVG7O+WW Kjwgjr+eXnhnhraR6NEjxGR+x8zQLjtHV/5DaL0= X-Google-Smtp-Source: ALg8bN5JOGUwXRFTSZbixwnXLfLvw6SzZun/iyX7h1Do+bRYcNnqGYIpRXVv5EI8IIE+PviDVlDMHpGEt1iYaDlek2A= X-Received: by 2002:a6b:db17:: with SMTP id t23mr2605267ioc.262.1546995669925; Tue, 08 Jan 2019 17:01:09 -0800 (PST) MIME-Version: 1.0 References: <20190108223024.GA147017@google.com> In-Reply-To: <20190108223024.GA147017@google.com> From: Oliver Date: Wed, 9 Jan 2019 12:00:58 +1100 Message-ID: Subject: Re: Kconfig label updates To: Bjorn Helgaas Cc: Tyrel Datwyler , linux-s390@vger.kernel.org, Heiko Carstens , Linux Kernel Mailing List , Paul Mackerras , linux-pci@vger.kernel.org, Martin Schwidefsky , linuxppc-dev Content-Type: text/plain; charset="UTF-8" Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Wed, Jan 9, 2019 at 9:31 AM Bjorn Helgaas wrote: > > 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? "RISC Platform Architecture" apparently. I couldn't find any documentation written in the last decade that uses the term so it's probably a hold-over from when pseries and iseries had separate hardware platforms. Replacing "RPA" with "pseries" would be the least confusing way to handle it. > 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