public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Avi Kivity <avi@redhat.com>, KVM list <kvm@vger.kernel.org>,
	kvm-ppc <kvm-ppc@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	Carsten Otte <carsteno@de.ibm.com>,
	"Roedel, Joerg" <Joerg.Roedel@amd.com>
Subject: Re: New git workflow
Date: Wed, 11 Apr 2012 14:50:29 -0500	[thread overview]
Message-ID: <4F85E085.7070705@freescale.com> (raw)
In-Reply-To: <20120411122322.GB5007@bloggs.ozlabs.ibm.com>

On 04/11/2012 07:23 AM, Paul Mackerras wrote:
> On Sun, Apr 08, 2012 at 02:33:32PM +0300, Avi Kivity wrote:
>> On 04/05/2012 08:02 PM, Avi Kivity wrote:
>>> I'll publish the new branches tomorrow, with any luck.
>>
>> There wasn't any luck, so it's only ready today.  To allow chance for
>> review, I'm publishing next as next-candidate.
>>
>> Paul/Alex, please review the powerpc bits.  Specifically:
>>
>>    system.h is gone, so I moved the prototype of load_up_fpu() to
>> <asm/switch_to.h>  and added a #include (8fae845f4956d).
>>    E6500 was added in upstream in parallel with the split of kvm
>> E500/E500MC.  I guessed which part of the #ifdef E6500 was to go into,
>> but please verify (73196cd364a2, 06aae86799c1b).
>
> All looks OK as far as I can see, but I have asked Scott Wood to
> double-check the e500/e500mc bits.

e6500 should have CPU_FTR_EMB_HV.  Otherwise looks OK.

-Scott

      reply	other threads:[~2012-04-11 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 17:02 New git workflow Avi Kivity
2012-04-06 12:02 ` Takuya Yoshikawa
2012-04-11  9:42   ` Avi Kivity
2012-04-08 11:33 ` Avi Kivity
2012-04-11 12:23   ` Paul Mackerras
2012-04-11 19:50     ` Scott Wood [this message]

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=4F85E085.7070705@freescale.com \
    --to=scottwood@freescale.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=carsteno@de.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=paulus@samba.org \
    /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