Thread (11 messages) 11 messages, 4 authors, 2008-12-23

Re: linux-next: manual merge of the kvm tree

From: Paul Mackerras <hidden>
Date: 2008-12-23 00:07:36

Hollis Blanchard writes:
On Tue, 2008-12-23 at 09:29 +1100, Paul Mackerras wrote:
quoted
Hollis Blanchard writes:
quoted
quoted
Patch is in Paulus -next already so we'll have to do a manual resolve.
Who has to do it? My code should "win".
Do you have your own tree or is all your stuff in the main kvm tree?

If there is a powerpc KVM tree, I could pull that and resolve the
conflict, but I don't want to pull all the queued up KVM stuff.
It's just the main KVM tree.
quoted
Worst case is Linus gets to resolve the conflict in the merge window.
If that's just a matter of him taking your version of the file, it
should be within his powers to manage. :)
Yeah, that's what I meant by "win"... whatever changes Ben made are to
now-dead code, so the code in kvm.git should be used. Does Linus need
special instruction to do this, or how does that work?
ppc44x_defconfig now fails to build in my tree because of _tlbil_all
being undefined (it has CONFIG_KVM=y), so I need some sort of fix.
What would happen if I made arch/powerpc/kvm/powerpc.c look like the
version from the KVM tree?

Paul.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help