From: ethan zhao <ethan.zhao@oracle.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
gleb@kernel.org, pbonzini@redhat.com, kvm@vger.kernel.org,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
david.vrabel@citrix.com, xen-devel@lists.xenproject.org,
alex.williamson@redhat.com, alexander.h.duyck@intel.com,
ethan.kernel@gmail.com
Subject: Re: [PATCH v3 0/4 resend] Introduce device assignment flag operation helper function
Date: Tue, 09 Sep 2014 09:48:28 +0800 [thread overview]
Message-ID: <540E5C6C.5060802@oracle.com> (raw)
In-Reply-To: <20140908170801.GP8080@google.com>
Bjorn,
Thanks, will fix the building issue for new version and resend.
Ethan
On 2014/9/9 1:08, Bjorn Helgaas wrote:
> On Fri, Sep 05, 2014 at 11:15:22AM -0600, Bjorn Helgaas wrote:
>> On Fri, Aug 08, 2014 at 01:36:03PM +0800, Ethan Zhao wrote:
>>> This patch set introduces three PCI device flag operation helper functions
>>> when set pci device PF/VF to assigned or deassigned status also check it.
>>> and patch 2,3,4 apply these helper functions to KVM,XEN and PCI.
>>>
>>> v2: simplify unnecessory ternary operation in function pci_is_dev_assigned().
>>> v3: amend helper function naming.
>>>
>>> Appreciate suggestion from
>>> alex.williamson@redhat.com,
>>> david.vrabel@citrix.com,
>>> alexander.h.duyck@intel.com
>>>
>>> Resend for v3.16 building.
>>>
>>> Thanks,
>>> Ethan
>>> ---
>>> Ethan Zhao (4):
>>> PCI: introduce helper functions for device flag operation
>>> KVM: use pci device flag operation helper functions
>>> xen-pciback: use pci device flag operation helper function
>>> PCI: use device flag operation helper function in iov.c
>>>
>>> drivers/pci/iov.c | 2 +-
>>> drivers/xen/xen-pciback/pci_stub.c | 4 ++--
>>> include/linux/pci.h | 13 +++++++++++++
>>> virt/kvm/assigned-dev.c | 2 +-
>>> virt/kvm/iommu.c | 4 ++--
>>> 5 files changed, 19 insertions(+), 6 deletions(-)
>>>
>> Applied to pci/virtualization for v3.18, thanks!
> I dropped these because of build errors from the kbuild-test robot. Fix
> and resend if you still want them.
>
> Bjorn
prev parent reply other threads:[~2014-09-09 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 5:36 [PATCH v3 0/4 resend] Introduce device assignment flag operation helper function Ethan Zhao
2014-08-08 5:36 ` [PATCH 1/4] PCI: introduce helper functions for device flag operation Ethan Zhao
2014-08-08 5:36 ` [PATCH 2/4] KVM: use pci device flag operation helper functions Ethan Zhao
2014-08-08 5:36 ` [PATCH 3/4] xen-pciback: use pci device flag operation helper function Ethan Zhao
2014-08-08 5:36 ` [PATCH 4/4] PCI: use device flag operation helper function in iov.c Ethan Zhao
2014-09-05 17:15 ` [PATCH v3 0/4 resend] Introduce device assignment flag operation helper function Bjorn Helgaas
2014-09-08 17:08 ` Bjorn Helgaas
2014-09-09 1:48 ` ethan zhao [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=540E5C6C.5060802@oracle.com \
--to=ethan.zhao@oracle.com \
--cc=alex.williamson@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ethan.kernel@gmail.com \
--cc=gleb@kernel.org \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=xen-devel@lists.xenproject.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).