On Thu, Jul 03, 2014 at 06:45:45PM +0100, Marc Zyngier wrote: > Hi Jason, > > On 30/06/14 16:50, Marc Zyngier wrote: > > Hi Jason, > > > > On 30/06/14 16:43, Jason Cooper wrote: > >> Marc, > >> > >> On Mon, Jun 30, 2014 at 04:01:29PM +0100, Marc Zyngier wrote: > >>> I now have received enough Reviewed-by from people familiar with the > >>> architecture, and a number of Tested-by from actual implementors, > >>> which (IMHO) makes ready for merging into 3.17 (Thomas, Jason: How do > >>> you want to play it? We have a rather big dependency between the first > >>> few patches and the rest of the stuff, which is KVM only). > >> > >> On a quick glance, it looks like patch #1 is conflict-prone and #2 crosses > >> outside of irqchip/. So, I could setup a topic branch for #1 that > >> we'll both use. Then I'll Ack #2 for you to take. Would that work for > >> you? > > > > That'd be absolutely great. Just point me to the topic branch you'd like > > to use, and I'll get it into the KVM/ARM tree. > > Sorry to pester you... Do you have any update on this? Christoffer and I > are putting our queue together for the next merge window, and I'd really > like to get this going before disappearing on holiday...
Hey, sorry for the delay. I'm just catching up from being sick over the long weekend. I'll go ahead and create irqchip/gic to hold all of the changes to the gic driver this time around. I'll add this series first since it's most ready to go and I'd like everything else to go on top of it. thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
