From: "Aneesh Kumar K.V" <aneesh.kumar@linux•vnet.ibm.com>
To: Alexander Graf <agraf@suse•de>
Cc: Paul Mackerras <paulus@samba•org>,
linuxppc-dev@lists•ozlabs.org, kvm-ppc@vger•kernel.org,
"kvm@vger•kernel.org mailing list" <kvm@vger•kernel.org>
Subject: Re: [PATCH -V2 06/14] kvm: powerpc: booke: Convert BOOKE to use kvmppc_ops callbacks
Date: Fri, 18 Oct 2013 10:14:17 +0530 [thread overview]
Message-ID: <87eh7jqjby.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <01BC643C-0AA9-47E8-A7E9-7A84AB280298@suse.de>
Alexander Graf <agraf@suse•de> writes:
> On 07.10.2013, at 18:47, Aneesh Kumar K.V <aneesh.kumar@linux•vnet.ibm.com> wrote:
>
>> From: "Aneesh Kumar K.V" <aneesh.kumar@linux•vnet.ibm.com>
>>
>> Make required changes to get BOOKE configs to build with
>> the introduction of kvmppc_ops callback
>>
>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux•vnet.ibm.com>
>
> This can not be a separate commit, as you're breaking bisectability for booke this way.
>
The only reason I split that into two was to make review easy. But yes
when merging to your tree we should fold.
> I've squashed this in with the previous commit.
>
Ok.
-aneesh
next prev parent reply other threads:[~2013-10-18 4:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 16:47 [PATCH -V2 00/14] Allow PR and HV KVM to coexist in one kernel Aneesh Kumar K.V
2013-10-07 16:47 ` [PATCH -V2 01/14] kvm: powerpc: book3s: remove kvmppc_handler_highmem label Aneesh Kumar K.V
2013-10-07 16:47 ` [PATCH -V2 02/14] kvm: powerpc: book3s: move book3s_64_vio_hv.c into the main kernel binary Aneesh Kumar K.V
2013-10-07 16:47 ` [PATCH -V2 03/14] kvm: powerpc: book3s: pr: Rename KVM_BOOK3S_PR to KVM_BOOK3S_PR_POSSIBLE Aneesh Kumar K.V
2013-10-07 16:47 ` [PATCH -V2 04/14] kvm: powerpc: book3s: Add a new config variable CONFIG_KVM_BOOK3S_HV_POSSIBLE Aneesh Kumar K.V
2013-10-07 16:47 ` [PATCH -V2 05/14] kvm: powerpc: book3s: Add kvmppc_ops callback Aneesh Kumar K.V
2013-10-07 16:47 ` [PATCH -V2 06/14] kvm: powerpc: booke: Convert BOOKE to use kvmppc_ops callbacks Aneesh Kumar K.V
2013-10-17 16:50 ` Alexander Graf
2013-10-18 4:44 ` Aneesh Kumar K.V [this message]
2013-10-07 16:47 ` [PATCH -V2 07/14] kvm: powerpc: book3s: Cleanup interrupt handling code Aneesh Kumar K.V
2013-10-07 16:47 ` [PATCH -V2 08/14] kvm: powerpc: book3s: Add is_hv_enabled to kvmppc_ops Aneesh Kumar K.V
2013-10-07 16:47 ` [PATCH -V2 09/14] kvm: powerpc: book3s: pr: move PR related tracepoints to a separate header Aneesh Kumar K.V
2013-10-07 16:47 ` [PATCH -V2 10/14] kvm: powerpc: booke: Move booke related tracepoints to " Aneesh Kumar K.V
2013-10-07 16:47 ` [PATCH -V2 11/14] kvm: powerpc: book3s: Support building HV and PR KVM as module Aneesh Kumar K.V
2013-10-17 5:11 ` Aneesh Kumar K.V
2013-10-07 16:48 ` [PATCH -V2 12/14] kvm: Add struct kvm arg to memslot APIs Aneesh Kumar K.V
2013-10-07 16:48 ` [PATCH -V2 13/14] kvm: powerpc: book3s: Allow the HV and PR selection per virtual machine Aneesh Kumar K.V
2013-10-07 16:48 ` [PATCH -V2 14/14] kvm: powerpc: book3s: drop is_hv_enabled Aneesh Kumar K.V
2013-10-15 9:00 ` [PATCH -V2 00/14] Allow PR and HV KVM to coexist in one kernel Aneesh Kumar K.V
2013-10-17 16:49 ` 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=87eh7jqjby.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux$(echo .)vnet.ibm.com \
--cc=agraf@suse$(echo .)de \
--cc=kvm-ppc@vger$(echo .)kernel.org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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