public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Paul Mackerras <paulus@samba.org>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Please pull powerpc KVM fixes
Date: Tue, 03 Apr 2012 17:10:47 +0300	[thread overview]
Message-ID: <4F7B04E7.60708@redhat.com> (raw)
In-Reply-To: <20120403122245.GD24141@bloggs.ozlabs.ibm.com>

On 04/03/2012 03:22 PM, Paul Mackerras wrote:
> On Tue, Apr 03, 2012 at 10:03:05PM +1000, Paul Mackerras wrote:
> > 
> > The following changes since commit 592f5d87b3feee9d60411f19d583038c0c7670ad:
>
> OK, I messed up the git request-pull command.  The request should have
> looked like this:
>
> The following changes since commit b1a808ff436343956a6ae63178ea1810c5e5a3a1:
>
>   Merge branch 'for-next' of git://gitorious.org/kernel-hsi/kernel-hsi (2012-04-02 09:50:40 -0700)
>
> are available in the git repository at:
>
>
>   git://github.com/paulusmack/linux tags/powerpc-fixes
>
> for you to fetch changes up to 592f5d87b3feee9d60411f19d583038c0c7670ad:
>
>   KVM: PPC: Book3S: PR: Fix preemption (2012-04-03 16:42:39 +1000)
>
> ----------------------------------------------------------------
> Five fixes for bugs that have crept in to the powerpc KVM implementations.
> These are all small simple patches that only affect arch/powerpc/kvm.
> They come from the series that Alex Graf put together but which was too
> late for the 3.4 merge window.
>
>

Thanks, pulled into kvm-updates/3.4.  Will post upstream after adding
x86 fixes.

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

  reply	other threads:[~2012-04-03 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 12:03 [GIT PULL] Please pull powerpc KVM fixes Paul Mackerras
2012-04-03 12:22 ` Paul Mackerras
2012-04-03 14:10   ` Avi Kivity [this message]
2012-04-05 16:05   ` Avi Kivity

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=4F7B04E7.60708@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --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