On 07/11/16 17:36, Kirti Wankhede wrote: > > > On 11/7/2016 11:45 AM, Alexey Kardashevskiy wrote: >> On 07/11/16 14:59, Kirti Wankhede wrote: >>> >>> >>> On 11/7/2016 9:00 AM, Alexey Kardashevskiy wrote: >>>> On 05/11/16 08:10, Kirti Wankhede wrote: > > ... > >>>>> >>>>> Patch series tested with linux-next upto commit 14970f204b19 @Fri Oct 28 >>>>> Resolved against conflicting change: >>>> >>>> Patch 11/22 does not apply if the patchset is applied on top of 14970f204b19. >>>> >>>> >>> >>> Pull commit 05692d7005a3 (below) commit. >> >> Nah, it was my fault, thunderbird's plugin saved mails in wrong order, >> false alarm, sorry. >> >> Speaking of order, 11/22 is better be squashed into 02/22 (as it does not >> seem to make sense alone; it also does not depend on something between >> 02/22 and 11/22); and both 01/22 and 02/22 better be moved where "docs" >> patches start as they do not makes sense earlier anyway, or do they? >> >> > > There are dependencies in the patch series: > Patch 10/22 depends on patch 01/22 and patch 03/22 to 09/22 patch. > > Patch 02/22 depends on patch 01/22. > > Patch 11/22 doesn't make sense without patch 10/22. > > Patch 12/22 depends on patch 11/22. > > Patch 13/22 to 18/22 are independent, pulling common code in functions. > But patch 21/22 uses these APIs in sample driver, so has to be before that. > > Patch 19/22 adds basic documentation. > Patch 21/22 depends on 19/22 patch because that adds sample driver and > its explanation to documentation. Ouch, I get it now, sorry. I was compiling on ppc64 and everything related to iommu type1 (i.e. x86) just got skipped. -- Alexey -- 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
