From: Julien Grall <julien.grall@citrix.com>
To: Manish Jaggi <mjaggi@caviumnetworks.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: edgar.iglesias@xilinx.com, xen-devel@lists.xenproject.org,
Josh.Whitehead@dornerworks.com, Ian.Campbell@citrix.com,
Robert VanVossen <robert.vanvossen@dornerworks.com>
Subject: Re: [PATCH v2] xen/passthrough: Support a single iommu_domain per xen domain per SMMU
Date: Mon, 30 Mar 2015 12:40:58 +0100 [thread overview]
Message-ID: <5519364A.50606@citrix.com> (raw)
In-Reply-To: <55192DC9.6060206@caviumnetworks.com>
Hello,
On 30/03/15 12:04, Manish Jaggi wrote:
>>> Julien/Ian could you please hold the merge of this patch.
>> Sorry Manish, but the Xen community works on a first come first served
>> basis: if/when this patch is considered in good condition and ready to
>> be merged, is likely to be merged.
>> Unless you have a specific concern about the code of course.
> Ok. I will incorporate robert's patch in my patch set.
Why we should wait you to sent your PCI SMMU changes? It will likely
take another couple of months before your series will be merged.
Robert's patch is a standalone patch which is useful for non-PCI case
(for instance 2 networks cards under the same SMMU).
He sent the v4 last week and the patch is ready to go in Xen tree.
Regards,
--
Julien Grall
prev parent reply other threads:[~2015-03-30 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 13:46 [PATCH v2] xen/passthrough: Support a single iommu_domain per xen domain per SMMU Robbie VanVossen
2015-03-23 21:53 ` Julien Grall
2015-03-24 15:07 ` Robert VanVossen
2015-03-24 15:19 ` Julien Grall
2015-03-24 11:07 ` Manish Jaggi
2015-03-24 14:04 ` Robert VanVossen
2015-03-25 4:58 ` Manish Jaggi
2015-03-25 17:35 ` Stefano Stabellini
2015-03-30 11:04 ` Manish Jaggi
2015-03-30 11:40 ` Julien Grall [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=5519364A.50606@citrix.com \
--to=julien.grall@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Josh.Whitehead@dornerworks.com \
--cc=edgar.iglesias@xilinx.com \
--cc=mjaggi@caviumnetworks.com \
--cc=robert.vanvossen@dornerworks.com \
--cc=stefano.stabellini@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.