From: Russell Currey <ruscur@russell.cc>
To: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>,
helgaas@kernel.org, bhelgaas@google.com,
benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au
Cc: seroyer@linux.vnet.ibm.com, jjalvare@linux.vnet.ibm.com,
alex.williamson@redhat.com, linux-pci@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, bodong@mellanox.com,
eli@mellanox.com, saeedm@mellanox.com
Subject: Re: [PATCH v5 0/3] Prepartion for SR-IOV PowerVM Enablement
Date: Mon, 04 Dec 2017 15:48:46 +1100 [thread overview]
Message-ID: <1512362926.1689.1.camel@russell.cc> (raw)
In-Reply-To: <20171109140035.64975-1-bryantly@linux.vnet.ibm.com>
On Thu, 2017-11-09 at 08:00 -0600, Bryant G. Ly wrote:
> v1 - Initial patch
> v2 - Addressed Bjorn's comment on creating a highly platform
> dependent global exported symbol.
> v3 - Based patch off linux-ppc/master
> v4 - Using the sriov-drivers_autoprobe mechanism per Bjorn's request
> v5 - Fixed comments and commit message
Looks good to me, for the whole series:
Acked-by: Russell Currey <ruscur@russell.cc>
>
> Bryant G. Ly (3):
> powerpc/kernel: Separate SR-IOV Calls
> pseries: Add PSeries SR-IOV Machine dependent calls
> PCI/IOV: Add pci_vf_drivers_autoprobe() interface
>
> 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 | 33 ++++++++++++++--
> ------------
> arch/powerpc/platforms/powernv/pci-ioda.c | 6 +++--
> arch/powerpc/platforms/pseries/eeh_pseries.c | 24
> ++++++++++++++++++++
> arch/powerpc/platforms/pseries/pci.c | 31
> ++++++++++++++++++++++----
> drivers/pci/iov.c | 11 ++++++++++
> include/linux/pci.h | 2 ++
> 11 files changed, 118 insertions(+), 33 deletions(-)
>
prev parent reply other threads:[~2017-12-04 4:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 14:00 [PATCH v5 0/3] Prepartion for SR-IOV PowerVM Enablement Bryant G. Ly
2017-11-09 14:00 ` [PATCH v5 1/3] powerpc/kernel: Separate SR-IOV Calls Bryant G. Ly
2017-12-12 11:39 ` [v5,1/3] " Michael Ellerman
2017-11-09 14:00 ` [PATCH v5 2/3] pseries: Add PSeries SR-IOV Machine dependent calls Bryant G. Ly
2017-11-09 14:00 ` [PATCH v5 3/3] PCI/IOV: Add pci_vf_drivers_autoprobe() interface Bryant G. Ly
2017-11-29 16:13 ` [PATCH v5 0/3] Prepartion for SR-IOV PowerVM Enablement Bryant G. Ly
2017-12-01 11:48 ` Michael Ellerman
2017-12-03 1:45 ` Alexey Kardashevskiy
2017-12-04 15:08 ` Bryant G. Ly
2017-12-05 1:24 ` Alexey Kardashevskiy
2017-12-05 15:13 ` Bryant G. Ly
2017-12-08 6:03 ` Alexey Kardashevskiy
2017-12-08 14:52 ` Bryant G. Ly
2017-12-04 4:48 ` Russell Currey [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=1512362926.1689.1.camel@russell.cc \
--to=ruscur@russell.cc \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=bodong@mellanox.com \
--cc=bryantly@linux.vnet.ibm.com \
--cc=eli@mellanox.com \
--cc=helgaas@kernel.org \
--cc=jjalvare@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=saeedm@mellanox.com \
--cc=seroyer@linux.vnet.ibm.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).