From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
kvm-ppc@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PULL 0/7] avi patch queue 2011-12-25
Date: Tue, 27 Dec 2011 09:45:37 +0000 [thread overview]
Message-ID: <4EF993C1.30704@redhat.com> (raw)
In-Reply-To: <1324810715-28312-1-git-send-email-agraf@suse.de>
On 12/25/2011 12:58 PM, Alexander Graf wrote:
> Hi Avi,
>
> Here are a couple compile/trivial fixes for PPC KVM. Please make sure
> they all get to 3.2, worst case through -stable.
>
> I left out all the other fine commits that would be great to have in
> upstream due to limited testing on my side still. But they definitely
> are not forgotten!
>
>
Which of these are needed for 3.1, 3.0?
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
kvm-ppc@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PULL 0/7] avi patch queue 2011-12-25
Date: Tue, 27 Dec 2011 11:45:37 +0200 [thread overview]
Message-ID: <4EF993C1.30704@redhat.com> (raw)
In-Reply-To: <1324810715-28312-1-git-send-email-agraf@suse.de>
On 12/25/2011 12:58 PM, Alexander Graf wrote:
> Hi Avi,
>
> Here are a couple compile/trivial fixes for PPC KVM. Please make sure
> they all get to 3.2, worst case through -stable.
>
> I left out all the other fine commits that would be great to have in
> upstream due to limited testing on my side still. But they definitely
> are not forgotten!
>
>
Which of these are needed for 3.1, 3.0?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-27 9:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 10:58 [PULL 0/7] avi patch queue 2011-12-25 Alexander Graf
2011-12-25 10:58 ` Alexander Graf
2011-12-25 10:58 ` [PATCH 1/7] KVM: PPC: Whitespace fix for kvm.h Alexander Graf
2011-12-25 10:58 ` Alexander Graf
2011-12-25 10:58 ` [PATCH 2/7] KVM: Fix whitespace in kvm_para.h Alexander Graf
2011-12-25 10:58 ` Alexander Graf
2011-12-25 10:58 ` [PATCH 3/7] powerpc/kvm: annotate kvm_rma_init as __init Alexander Graf
2011-12-25 10:58 ` Alexander Graf
2011-12-25 10:58 ` [PATCH 4/7] KVM: PPC: move compute_tlbie_rb to book3s_64 common header Alexander Graf
2011-12-25 10:58 ` Alexander Graf
2011-12-25 10:58 ` [PATCH 5/7] KVM: PPC: protect use of kvmppc_h_pr Alexander Graf
2011-12-25 10:58 ` Alexander Graf
2011-12-25 10:58 ` [PATCH 6/7] powerpc kvm: fix kvmppc_start_thread() for CONFIG_SMP=N Alexander Graf
2011-12-25 10:58 ` Alexander Graf
2011-12-25 10:58 ` [PATCH 7/7] KVM: PPC: e500: include linux/export.h Alexander Graf
2011-12-25 10:58 ` Alexander Graf
2011-12-25 11:03 ` [PULL 0/7] avi patch queue 2011-12-25 Avi Kivity
2011-12-25 11:03 ` Avi Kivity
2011-12-25 11:29 ` Alexander Graf
2011-12-25 11:29 ` Alexander Graf
2011-12-25 11:32 ` Avi Kivity
2011-12-25 11:32 ` Avi Kivity
2011-12-25 11:33 ` Avi Kivity
2011-12-25 11:33 ` Avi Kivity
2011-12-27 9:45 ` Avi Kivity [this message]
2011-12-27 9:45 ` Avi Kivity
2012-01-09 12:48 ` Alexander Graf
2012-01-09 12:48 ` Alexander Graf
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=4EF993C1.30704@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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.