linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ray Jui <rjui@broadcom.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Scott Branden <sbranden@broadcom.com>,
	<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<bcm-kernel-feedback-list@broadcom.com>,
	Ray Jui <rjui@broadcom.com>
Subject: [PATCH v2 0/2] iProc PCIe driver Kconfig changes
Date: Wed, 25 Mar 2015 00:08:11 -0700	[thread overview]
Message-ID: <1427267293-29585-1-git-send-email-rjui@broadcom.com> (raw)

This patch series contains two patches to address iProc PCIe Kconfig related
issues. The first patch adds more protection to PCIE_IPROC so it cannot be
accidentally enabled for non-ARM based platforms. The second patch changes the
config name of the iProc PCIe platform driver from PCIE_IPROC_PLTFM to
PCIE_IPROC_PLATFORM. The driver name is also changed from pcie-iproc-pltfm.c
to pcie-iproc-platform.c so it's consistent with the config name change.

Changes from v1:
 - Changes the driver name from pcie-iproc-pltfm.c to pcie-iproc-platform.c

Ray Jui (2):
  pci: iproc: fix PCIE_IPROC in Kconfig
  pci: iproc: change PCIE_IPROC_PLTFM to PCIE_IPROC_PLATFORM

 drivers/pci/host/Kconfig                           |    4 +++-
 drivers/pci/host/Makefile                          |    2 +-
 .../{pcie-iproc-pltfm.c => pcie-iproc-platform.c}  |    0
 3 files changed, 4 insertions(+), 2 deletions(-)
 rename drivers/pci/host/{pcie-iproc-pltfm.c => pcie-iproc-platform.c} (100%)

-- 
1.7.9.5


             reply	other threads:[~2015-03-25  7:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  7:08 Ray Jui [this message]
2015-03-25  7:08 ` [PATCH v2 1/2] pci: iproc: fix PCIE_IPROC in Kconfig Ray Jui
2015-03-25  7:08 ` [PATCH v2 2/2] pci: iproc: change PCIE_IPROC_PLTFM to PCIE_IPROC_PLATFORM Ray Jui
2015-03-27 16:24 ` [PATCH v2 0/2] iProc PCIe driver Kconfig changes Ray Jui
2015-04-08 17:13   ` Bjorn Helgaas
2015-04-08 17:24     ` Ray Jui

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=1427267293-29585-1-git-send-email-rjui@broadcom.com \
    --to=rjui@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sbranden@broadcom.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).