From: Cornelia Huck <cohuck@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: move KVM_CAP_NR_MEMSLOTS to common code
Date: Tue, 2 Apr 2019 13:57:48 +0200 [thread overview]
Message-ID: <20190402135748.5d845872.cohuck@redhat.com> (raw)
In-Reply-To: <1553793000-53968-1-git-send-email-pbonzini@redhat.com>
On Thu, 28 Mar 2019 18:10:00 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:
> All architectures except MIPS were defining it in the same way,
> and memory slots are handled entirely by common code so there
> is no point in keeping the definition per-architecture.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> Documentation/virtual/kvm/api.txt | 5 ++---
> arch/powerpc/kvm/powerpc.c | 3 ---
> arch/s390/kvm/kvm-s390.c | 3 ---
> arch/x86/kvm/x86.c | 3 ---
> virt/kvm/arm/arm.c | 3 ---
> virt/kvm/kvm_main.c | 2 ++
> 6 files changed, 4 insertions(+), 15 deletions(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2019-04-02 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 17:10 [PATCH] kvm: move KVM_CAP_NR_MEMSLOTS to common code Paolo Bonzini
2019-03-29 9:43 ` David Hildenbrand
2019-04-02 11:57 ` Cornelia Huck [this message]
2019-04-02 14:51 ` Sean Christopherson
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=20190402135748.5d845872.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox