From: Marc Zyngier <maz@kernel.org>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: Drop stale kvm_is_transparent_hugepage() declaration
Date: Mon, 18 Oct 2021 16:18:36 +0100 [thread overview]
Message-ID: <87y26qnyyb.wl-maz@kernel.org> (raw)
In-Reply-To: <20211018151407.2107363-1-vkuznets@redhat.com>
On Mon, 18 Oct 2021 16:14:07 +0100,
Vitaly Kuznetsov <vkuznets@redhat.com> wrote:
>
> kvm_is_transparent_hugepage() was removed in commit 205d76ff0684 ("KVM:
> Remove kvm_is_transparent_hugepage() and PageTransCompoundMap()") but its
> declaration in include/linux/kvm_host.h persisted. Drop it.
>
> Fixes: 205d76ff0684 (""KVM: Remove kvm_is_transparent_hugepage() and PageTransCompoundMap()")
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> ---
> include/linux/kvm_host.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> index 0f18df7fe874..2dc62a8cc96c 100644
> --- a/include/linux/kvm_host.h
> +++ b/include/linux/kvm_host.h
> @@ -1164,7 +1164,6 @@ int kvm_cpu_has_pending_timer(struct kvm_vcpu *vcpu);
>
> bool kvm_is_reserved_pfn(kvm_pfn_t pfn);
> bool kvm_is_zone_device_pfn(kvm_pfn_t pfn);
> -bool kvm_is_transparent_hugepage(kvm_pfn_t pfn);
>
> struct kvm_irq_ack_notifier {
> struct hlist_node link;
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-10-18 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 15:14 [PATCH] KVM: Drop stale kvm_is_transparent_hugepage() declaration Vitaly Kuznetsov
2021-10-18 15:18 ` Marc Zyngier [this message]
2021-12-07 9:15 ` Marc Zyngier
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=87y26qnyyb.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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;
as well as URLs for NNTP newsgroup(s).