From: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Alexander Graf <agraf-l3A5Bk7waGM@public.gmane.org>
Cc: "kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org list"
<kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Subject: Re: [PULL 0/3] PPC BookE patches
Date: Thu, 14 Oct 2010 18:07:04 +0200 [thread overview]
Message-ID: <4CB72AA8.4060506@redhat.com> (raw)
In-Reply-To: <1286707477-24676-1-git-send-email-agraf-l3A5Bk7waGM@public.gmane.org>
On 10/10/2010 12:44 PM, Alexander Graf wrote:
> Hi Marcelo / Avi,
>
> Scott has found some bugs in the BookE implementation of KVM, so please pull
> the fixes for them to the kvm tree.
>
> The following changes since commit 3c4504636ab1ff41ec162980bf85121aee14e58f:
> Huang Ying (1):
> KVM: MCE: Send SRAR SIGBUS directly
>
> are available in the git repository at:
>
> git://github.com/agraf/linux-2.6.git kvm-ppc-next
>
> Scott Wood (3):
> KVM: PPC: BookE: Load the lower half of MSR
> KVM: PPC: BookE: fix sleep with interrupts disabled
> KVM: PPC: e500: Call kvm_vcpu_uninit() before kvmppc_e500_tlb_uninit().
>
Pulled, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-10-14 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 10:44 [PULL 0/3] PPC BookE patches Alexander Graf
2010-10-10 10:44 ` [PATCH 1/3] KVM: PPC: BookE: Load the lower half of MSR Alexander Graf
2010-10-10 10:44 ` [PATCH 2/3] KVM: PPC: BookE: fix sleep with interrupts disabled Alexander Graf
[not found] ` <1286707477-24676-1-git-send-email-agraf-l3A5Bk7waGM@public.gmane.org>
2010-10-10 10:44 ` [PATCH 3/3] KVM: PPC: e500: Call kvm_vcpu_uninit() before kvmppc_e500_tlb_uninit() Alexander Graf
2010-10-14 16:07 ` Avi Kivity [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=4CB72AA8.4060506@redhat.com \
--to=avi-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=agraf-l3A5Bk7waGM@public.gmane.org \
--cc=kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.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