linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Avi Kivity <avi@qumranet.com>,
	linux-next@vger.kernel.org,
	Kumar Gala <galak@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: linux-next: manual merge of the kvm tree
Date: Tue, 23 Dec 2008 09:11:05 +1100	[thread overview]
Message-ID: <1229983865.4360.23.camel@pasglop> (raw)
In-Reply-To: <1229983422.7181.7.camel@localhost.localdomain>

On Mon, 2008-12-22 at 16:03 -0600, Hollis Blanchard wrote:
> > Patch is in Paulus -next already so we'll have to do a manual
> resolve.
> 
> Who has to do it? My code should "win".

I don't understand. There is no "win" or "lose" here, just somebody who
has to fixup the merge conflict :-) In any case I don't see why any code
should "win" here.

Shouldn't be hard, we just need to sync with paulus who pulls what tree
in what tree to solve it. Maybe we can pull kvm into powerpc and solve
it there or something like that ?

The other solution is to rebase powerpc and change the patch but that's
evil, we always avoid rebasing, it hurts too many people.

> > Also, you'll need to include ../mm/mmu_decl.h to get to _tlbil_* ..
> > sorry about that.
> 
> I don't want _tlb anything; I was only using _tlbia(), and I'm not any
> more.

Ok. I got confused by another mail about undefined _tlbil_all() which
was probably another fix for that same stuff.

Cheers,
Ben.

  reply	other threads:[~2008-12-22 22:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22  3:52 linux-next: manual merge of the kvm tree Stephen Rothwell
2008-12-22  5:13 ` Benjamin Herrenschmidt
2008-12-22 21:39   ` Hollis Blanchard
2008-12-22 21:41     ` Benjamin Herrenschmidt
2008-12-22 22:03       ` Hollis Blanchard
2008-12-22 22:11         ` Benjamin Herrenschmidt [this message]
2008-12-22 22:29         ` Paul Mackerras
2008-12-22 22:44           ` Hollis Blanchard
2008-12-23  0:07             ` Paul Mackerras
2008-12-23  1:02               ` Hollis Blanchard
2008-12-23  1:38                 ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2009-06-12  2:57 Stephen Rothwell
2009-06-12  7:19 ` Avi Kivity
2009-01-02  0:44 Stephen Rothwell
2008-12-29  5:11 Stephen Rothwell
2008-11-25  6:49 Stephen Rothwell
2008-10-29  2:58 Stephen Rothwell
2008-10-29  9:55 ` Avi Kivity
2008-10-29 10:35   ` Stephen Rothwell
2008-10-15  5:27 Stephen Rothwell
2008-09-17  5:50 Stephen Rothwell
2008-09-17  5:24 Stephen Rothwell
2008-09-15  0:14 Stephen Rothwell
2008-09-15  6:53 ` Ingo Molnar
2008-09-12 19:50 Stephen Rothwell
2008-09-12 19:53 ` Arjan van de Ven
2008-09-12 19:59 ` Stephen Rothwell
2008-08-26  4:45 Stephen Rothwell
2008-08-26  7:39 ` Avi Kivity
2008-08-26  7:41   ` Stephen Rothwell
2008-08-15  4:46 Stephen Rothwell
2008-08-04  3:13 Stephen Rothwell
2008-07-22  3:43 Stephen Rothwell

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=1229983865.4360.23.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=avi@qumranet.com \
    --cc=galak@kernel.crashing.org \
    --cc=hollisb@us.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).