linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: linux-pci@vger.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: [PATCH] PCI: PCIE: Rename option title to something less confusing
Date: Fri, 5 Jul 2013 15:11:36 -0600	[thread overview]
Message-ID: <20130705211136.GA16551@google.com> (raw)
In-Reply-To: <1372970720-14016-1-git-send-email-ezequiel.garcia@free-electrons.com>

On Thu, Jul 04, 2013 at 05:45:20PM -0300, Ezequiel Garcia wrote:
> The previous option title "PCI Express support" is confusing.
> The name seems to imply this option is required to get PCIe support,
> which is not true.
> 
> Fix it to "PCI Express Port Bus support" which is more accurate.
> 
> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>

Applied to pci/misc for v3.12, thanks!  I'll rebase and push this branch
after v3.11-rc1 is released.

> ---
>  drivers/pci/pcie/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/pci/pcie/Kconfig b/drivers/pci/pcie/Kconfig
> index 569f82f..a82e70a 100644
> --- a/drivers/pci/pcie/Kconfig
> +++ b/drivers/pci/pcie/Kconfig
> @@ -2,7 +2,7 @@
>  # PCI Express Port Bus Configuration
>  #
>  config PCIEPORTBUS
> -	bool "PCI Express support"
> +	bool "PCI Express Port Bus support"
>  	depends on PCI
>  	help
>  	  This automatically enables PCI Express Port Bus support. Users can
> -- 
> 1.8.1.5
> 

      reply	other threads:[~2013-07-05 21:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 20:45 [PATCH] PCI: PCIE: Rename option title to something less confusing Ezequiel Garcia
2013-07-05 21:11 ` Bjorn Helgaas [this message]

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=20130705211136.GA16551@google.com \
    --to=bhelgaas@google.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).