On Sun, Feb 07, 2010 at 02:22:35PM +0200, Avi Kivity wrote: > On 02/05/2010 01:01 PM, Joerg Roedel wrote: >> >>> Yes, addresses the concern. >>> >> Are there any further objections against this patchset? If not it would >> be cool if you could give me some acks for the kvm specific parts of >> this patchset. >> > > There are two ways we can get the kvm bits in: > > - you publish a git tree excluding the kvm patches, I merge your tree, > then apply the kvm specific patches. This is best for avoiding > merge-time conflicts if I get other patches for the same area. > - you push everything including the kvm bits. > > I'm fine with both, though prefer the former. If you choose the latter, > ACK for the kvm patches. Hmm, the patch set is self-contained and hard to split. We had the same problem with the initial iommu-api merge. Since I have further updates for the AMD IOMMU driver I think its best to send the these patches and my updates directly to Linus after the KVM updates are merged in the next merge window. Thanks for your ACKs :-) Joerg -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
