From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoffer Dall Subject: Re: [PATCH v6 01/21] irqchip: ARM: GIC: Move some bits of GICv2 to a library-type file Date: Fri, 11 Jul 2014 23:41:56 +0200 Message-ID: References: <1404140510-5382-1-git-send-email-marc.zyngier@arm.com> <1404140510-5382-2-git-send-email-marc.zyngier@arm.com> <20140708223145.GG13433@titan.lakedaemon.net> <20140711161550.GA2093@cbox> <53C04D4F.5000605@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Jason Cooper , Marc Zyngier , "linux-arm-kernel@lists.infradead.org" , "kvmarm@lists.cs.columbia.edu" , "kvm@vger.kernel.org" , Mark Rutland , Catalin Marinas , Will Deacon , Thomas Gleixner To: Paolo Bonzini Return-path: Received: from mail-ig0-f174.google.com ([209.85.213.174]:42718 "EHLO mail-ig0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752497AbaGKVl5 (ORCPT ); Fri, 11 Jul 2014 17:41:57 -0400 Received: by mail-ig0-f174.google.com with SMTP id c1so274256igq.7 for ; Fri, 11 Jul 2014 14:41:56 -0700 (PDT) In-Reply-To: <53C04D4F.5000605@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 11 July 2014 22:47, Paolo Bonzini wrote: > Il 11/07/2014 18:15, Christoffer Dall ha scritto: > >> Thanks, I've pushed >> >> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git queue >> >> >> which will pretty much be the pull request to kvm/next (still need to >> test a few bits before moving to next and make it stable to be included >> in kvm/next). >> >> Will coordinate with Paolo to make sure commit >> 021f653791ad17e03f98aaa7fb933816ae16f161 lands in Linus' tree before >> sending the KVM pull-request. > > > So I'll send out the KVM changes early when the merge window open, and then > pull from you and send the result to Linus in a second request. Ok? > That's fine, I guess the only downside on my end would be a slight delay in getting the patches into kvm/next, but I don't even think anyone is eager waiting to update qemu headers or anything like that. So as long as the second pull request (with my changes) comes after the patches mentioned above land in Linus tree, I think we're all good. If anyone feels like taking a quick peek at the queue branch in the kvmarm tree to ensure I'm not messing this up, it would be appreciated. Thanks, -Christoffer From mboxrd@z Thu Jan 1 00:00:00 1970 From: christoffer.dall@linaro.org (Christoffer Dall) Date: Fri, 11 Jul 2014 23:41:56 +0200 Subject: [PATCH v6 01/21] irqchip: ARM: GIC: Move some bits of GICv2 to a library-type file In-Reply-To: <53C04D4F.5000605@redhat.com> References: <1404140510-5382-1-git-send-email-marc.zyngier@arm.com> <1404140510-5382-2-git-send-email-marc.zyngier@arm.com> <20140708223145.GG13433@titan.lakedaemon.net> <20140711161550.GA2093@cbox> <53C04D4F.5000605@redhat.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 11 July 2014 22:47, Paolo Bonzini wrote: > Il 11/07/2014 18:15, Christoffer Dall ha scritto: > >> Thanks, I've pushed >> >> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git queue >> >> >> which will pretty much be the pull request to kvm/next (still need to >> test a few bits before moving to next and make it stable to be included >> in kvm/next). >> >> Will coordinate with Paolo to make sure commit >> 021f653791ad17e03f98aaa7fb933816ae16f161 lands in Linus' tree before >> sending the KVM pull-request. > > > So I'll send out the KVM changes early when the merge window open, and then > pull from you and send the result to Linus in a second request. Ok? > That's fine, I guess the only downside on my end would be a slight delay in getting the patches into kvm/next, but I don't even think anyone is eager waiting to update qemu headers or anything like that. So as long as the second pull request (with my changes) comes after the patches mentioned above land in Linus tree, I think we're all good. If anyone feels like taking a quick peek at the queue branch in the kvmarm tree to ensure I'm not messing this up, it would be appreciated. Thanks, -Christoffer