From: Paolo Bonzini <pbonzini@redhat.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Gleb Natapov <gleb@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [PATCH 2/3] arm/arm64: KVM: MMIO support for BE guest
Date: Mon, 11 Nov 2013 16:10:35 +0100 [thread overview]
Message-ID: <5280F36B.5040501@redhat.com> (raw)
In-Reply-To: <CAMJs5B8S+m8bJfokBycMWXUcXSPT-S25_nq241=Ots7kzkjN7Q@mail.gmail.com>
Il 11/11/2013 15:56, Christoffer Dall ha scritto:
>> > Christoffer and Marc, please coordinate so that arm+arm64 patch go only
>> > through one person. The conflict between your two pull requests was not
>> > really necessary.
>> >
> I don't think the same patch was in both pull requests, right?
No, this patch conflicted with "arm/arm64: KVM: PSCI: use MPIDR to
identify a target CPU" from your tree. Both touched
arch/arm/include/asm/kvm_emulate.h and arch/arm64/include/asm/kvm_emulate.h
> Is what you're saying that any patch that touches arm and arm64 should
> always come from one of us so that you reduce the chance of a merge
> conflict?
Yes---note that it doesn't have to be *always* the same person; whatever
works best for you probably works best for me too. In this case all of
them were written by Marc, it would have been even simpler for you to
just give your Acked-by instead of picking up "arm/arm64: KVM: PSCI: use
MPIDR to identify a target CPU".
> There would still be the case where I carry those arm/arm64
> patches but th arm64 changes conflict with those in Marc's tree, no?
Yes, that can still happen. Conflicts are not bad, only inconsistencies
are.
Paolo
next prev parent reply other threads:[~2013-11-11 15:10 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 [this message]
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
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=5280F36B.5040501@redhat.com \
--to=pbonzini@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.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