All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: KVM list <kvm@vger.kernel.org>, kvm-ppc <kvm-ppc@vger.kernel.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Alexander Graf <agraf@suse.de>, Paul Mackerras <paulus@samba.org>,
	Carsten Otte <carsteno@de.ibm.com>,
	"Roedel, Joerg" <Joerg.Roedel@amd.com>
Subject: Re: New git workflow
Date: Sun, 08 Apr 2012 11:33:32 +0000	[thread overview]
Message-ID: <4F81778C.4050202@redhat.com> (raw)
In-Reply-To: <4F7DD034.5090102@redhat.com>

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).

Please either post fixup patches atop next-candidate, if needed, or
(preferably) post a new tree of the powerpc update based on
b6d33834bd4e, to replace b6d33834bd4e..966cd0f3bdd.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: KVM list <kvm@vger.kernel.org>, kvm-ppc <kvm-ppc@vger.kernel.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Alexander Graf <agraf@suse.de>, Paul Mackerras <paulus@samba.org>,
	Carsten Otte <carsteno@de.ibm.com>,
	"Roedel, Joerg" <Joerg.Roedel@amd.com>
Subject: Re: New git workflow
Date: Sun, 08 Apr 2012 14:33:32 +0300	[thread overview]
Message-ID: <4F81778C.4050202@redhat.com> (raw)
In-Reply-To: <4F7DD034.5090102@redhat.com>

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).

Please either post fixup patches atop next-candidate, if needed, or
(preferably) post a new tree of the powerpc update based on
b6d33834bd4e, to replace b6d33834bd4e..966cd0f3bdd.

-- 
error compiling committee.c: too many arguments to function

  parent reply	other threads:[~2012-04-08 11:33 UTC|newest]

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

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=4F81778C.4050202@redhat.com \
    --to=avi@redhat.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=agraf@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.