From: Andrew Jones <drjones@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/3] arm/arm64: KVM: MMIO support for BE guest
Date: Tue, 12 Nov 2013 10:41:58 +0100 [thread overview]
Message-ID: <20131112094157.GA2377@hawk.usersys.redhat.com> (raw)
In-Reply-To: <528124DA.5030303@redhat.com>
On Mon, Nov 11, 2013 at 07:41:30PM +0100, Paolo Bonzini wrote:
> Il 11/11/2013 19:26, Marc Zyngier ha scritto:
> >> > The pull requests were clean and my life wasn't complicated much... On
> >> > the other hand I'm trying to understand if there's something that can be
> >> > improved because the conflict surprised me. Right now, in fact, it's
> >> > not even entirely clear to me why ARM and ARM64 have separate maintainers.
> > Mostly because arm64 was developed and merged before any kind of useful
> > documentation was publicly available. As I've written most of the code,
> > it was only logical that I'd assume responsibility for it.
>
> That was my understanding as well.
>
> > Christoffer and I are actually working quite well together, and I don't
> > think there is much to improve, short of sharing a common git tree. And
> > to be perfectly clear, I wouldn't mind if we were written down as
> > co-maintainers for both ports...
>
> Then go for it. :) Send a patch to MAINTAINERS, get an Acked-by from
> Christoffer and I'll apply it.
>
> Gleb and I share the git tree and hand it off "formally" by email every
> 1 or 2 weeks to the other person. After the email is sent, the sender
> should no longer push to the shared tree. This however is by no means
> the only way to proceed, having separate trees and sending separate pull
> requests works well too. I would not mind the occasional conflict, and
> I'd be hardly surprised.
I'd cast my vote (if I have one) towards the sharing a tree method. For
those of us scrambling to get caught up with kvmarm, a reduction in the
number of trees and branches we need to track would be a welcome change.
drew
next prev parent reply other threads:[~2013-11-12 9:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 10:07 [GIT PULL] KVM/arm64 fixes for 3.13 Marc Zyngier
2013-11-08 10:07 ` [PATCH 1/3] arm64: KVM: Yield CPU when vcpu executes a WFE Marc Zyngier
2013-11-08 10:07 ` [PATCH 2/3] arm/arm64: KVM: MMIO support for BE guest Marc Zyngier
2013-11-11 11:04 ` Paolo Bonzini
2013-11-11 14:56 ` Christoffer Dall
2013-11-11 15:10 ` Paolo Bonzini
2013-11-11 15:49 ` Christoffer Dall
2013-11-11 17:56 ` Paolo Bonzini
2013-11-11 18:03 ` Peter Maydell
2013-11-11 18:05 ` Paolo Bonzini
2013-11-11 18:26 ` Marc Zyngier
2013-11-11 18:41 ` Christoffer Dall
2013-11-11 18:41 ` Paolo Bonzini
2013-11-12 9:41 ` Andrew Jones [this message]
2013-11-12 10:03 ` Marc Zyngier
2013-11-12 10:07 ` Paolo Bonzini
2013-11-12 16:30 ` Christoffer Dall
2013-11-11 18:39 ` Christoffer Dall
2013-11-08 10:07 ` [PATCH 3/3] arm/arm64: KVM: PSCI: propagate caller endianness to the incoming vcpu Marc Zyngier
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=20131112094157.GA2377@hawk.usersys.redhat.com \
--to=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox