From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>,
helgaas@kernel.org, bhelgaas@google.com,
benh@kernel.crashing.org, paulus@samba.org
Cc: jjalvare@linux.vnet.ibm.com, linux-pci@vger.kernel.org,
saeedm@mellanox.com, alex.williamson@redhat.com,
seroyer@linux.vnet.ibm.com,
"Bryant G. Ly" <bryantly@linux.vnet.ibm.com>,
eli@mellanox.com, "Juan J . Alvarez" <jjalvare@us.ibm.com>,
linuxppc-dev@lists.ozlabs.org, bodong@mellanox.com
Subject: Re: [v5,1/3] powerpc/kernel: Separate SR-IOV Calls
Date: Tue, 12 Dec 2017 22:39:24 +1100 (AEDT) [thread overview]
Message-ID: <3ywyXX5ZKtz9t6n@ozlabs.org> (raw)
In-Reply-To: <20171109140035.64975-2-bryantly@linux.vnet.ibm.com>
On Thu, 2017-11-09 at 14:00:33 UTC, "Bryant G. Ly" wrote:
> SR-IOV can now be enabled in PowerNV platforms and Pseries
> platforms. Therefore, the appropriate calls were moved to
> machine dependent code instead of definition at compile time.
>
> Signed-off-by: Bryant G. Ly <bryantly@linux.vnet.ibm.com>
> Signed-off-by: Juan J. Alvarez <jjalvare@us.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/988fc3ba5653278a8c14d6ccf68737
cheers
next prev parent reply other threads:[~2017-12-12 11:39 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 ` Michael Ellerman [this message]
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
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=3ywyXX5ZKtz9t6n@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--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=jjalvare@us.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).