From: Gleb Natapov <gleb@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc@vger.kernel.org, KVM list <kvm@vger.kernel.org>
Subject: Re: [PULL 0/8] ppc patch queue 2013-01-10
Date: Thu, 17 Jan 2013 13:28:32 +0200 [thread overview]
Message-ID: <20130117112832.GA31120@redhat.com> (raw)
In-Reply-To: <B52775F5-CFF4-42DE-921F-2CA2979C7B3C@suse.de>
On Thu, Jan 17, 2013 at 11:53:38AM +0100, Alexander Graf wrote:
>
> On 14.01.2013, at 10:03, Gleb Natapov wrote:
>
> > On Thu, Jan 10, 2013 at 01:45:04PM +0100, Alexander Graf wrote:
> >> Hi Marcelo / Gleb,
> >>
> >> This is my current patch queue for ppc. Please pull.
> >>
> >> Highlights this time:
> >>
> >> - Book3S: enable potential sPAPR guest emulation on PR KVM on pHyp
> >> - BookE: EPR (External Proxy Register) support
> >>
> >> Alex
> >>
> > Pulled, thanks.
>
> Any particular reason I don't see it in kvm/next?
>
Not pushed yet. Sorry. Autotesting now and will push today.
--
Gleb.
prev parent reply other threads:[~2013-01-17 11:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 12:45 [PULL 0/8] ppc patch queue 2013-01-10 Alexander Graf
2013-01-10 12:45 ` [PATCH 1/8] KVM: PPC: Fix SREGS documentation reference Alexander Graf
2013-01-10 12:45 ` [PATCH 2/8] KVM: PPC: Only WARN on invalid emulation Alexander Graf
2013-01-10 12:45 ` [PATCH 3/8] KVM: PPC: Book3S: PR: Enable alternative instruction for SC 1 Alexander Graf
2013-01-10 12:45 ` [PATCH 4/8] KVM: PPC: Fix mfspr/mtspr MMUCFG emulation Alexander Graf
2013-01-10 12:45 ` [PATCH 5/8] KVM: PPC: BookE: Allow irq deliveries to inject requests Alexander Graf
2013-01-10 12:45 ` [PATCH 6/8] KVM: PPC: BookE: Emulate mfspr on EPR Alexander Graf
2013-01-10 12:45 ` [PATCH 7/8] KVM: PPC: BookE: Implement EPR exit Alexander Graf
2013-01-10 12:45 ` [PATCH 8/8] KVM: PPC: BookE: Add EPR ONE_REG sync Alexander Graf
2013-01-14 9:03 ` [PULL 0/8] ppc patch queue 2013-01-10 Gleb Natapov
2013-01-17 10:53 ` Alexander Graf
2013-01-17 11:28 ` Gleb Natapov [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=20130117112832.GA31120@redhat.com \
--to=gleb@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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