From: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>
To: bhelgaas@google.com, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au
Cc: linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
"Bryant G. Ly" <bryantly@linux.vnet.ibm.com>
Subject: [PATCH v1 0/3] Prepartion for SR-IOV PowerVM Enablement
Date: Mon, 18 Sep 2017 14:26:48 -0500 [thread overview]
Message-ID: <20170918192651.78404-1-bryantly@linux.vnet.ibm.com> (raw)
This patch series is to prepare for enabling SR-IOV
on pseries. It separates the calls to be machine dependent
and does not change any current functionality.
Bryant G. Ly (3):
powerpc/kernel: Split up pci_bus_add_device
pseries: Override pci_bus_match_virtfn_driver
powerpc/kernel: Separate SR-IOV Calls
arch/powerpc/include/asm/machdep.h | 7 ++++
arch/powerpc/include/asm/pci-bridge.h | 4 +--
arch/powerpc/kernel/eeh_driver.c | 4 +--
arch/powerpc/kernel/pci-common.c | 23 +++++++++++++
arch/powerpc/kernel/pci_dn.c | 6 ----
arch/powerpc/platforms/powernv/eeh-powernv.c | 34 ++++++++++---------
arch/powerpc/platforms/powernv/pci-ioda.c | 6 ++--
arch/powerpc/platforms/pseries/pci.c | 17 ++++++++++
drivers/pci/bus.c | 51 +++++++++++++++++++++++-----
drivers/pci/iov.c | 2 +-
include/linux/pci.h | 3 ++
11 files changed, 118 insertions(+), 39 deletions(-)
--
2.11.0 (Apple Git-81)
next reply other threads:[~2017-09-18 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 19:26 Bryant G. Ly [this message]
2017-09-18 19:26 ` [PATCH v1 1/3] powerpc/kernel: Split up pci_bus_add_device Bryant G. Ly
2017-09-20 5:31 ` kbuild test robot
2017-09-21 20:43 ` Bjorn Helgaas
2017-09-22 13:46 ` Bryant G. Ly
2017-09-18 19:26 ` [PATCH v1 2/3] pseries: Override pci_bus_match_virtfn_driver Bryant G. Ly
2017-09-18 19:26 ` [PATCH v1 3/3] powerpc/kernel: Separate SR-IOV Calls Bryant G. Ly
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=20170918192651.78404-1-bryantly@linux.vnet.ibm.com \
--to=bryantly@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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).