From: Sean Christopherson <seanjc@google.com>
To: "'Guanjun'" <guanjun@linux.alibaba.com>
Cc: dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, kirill.shutemov@linux.intel.com,
yu.c.zhang@linux.intel.com, tabba@google.com,
xiaoyao.li@intel.com, pbonzini@redhat.com, x86@kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] KVM: Move kvm_gmem_migrate_folio inside CONFIG_MIGRATION
Date: Mon, 11 Dec 2023 07:15:35 -0800 [thread overview]
Message-ID: <ZXcnlzDhcy8_CizZ@google.com> (raw)
In-Reply-To: <20231211030518.2722714-1-guanjun@linux.alibaba.com>
On Mon, Dec 11, 2023, 'Guanjun' wrote:
> From: Guanjun <guanjun@linux.alibaba.com>
>
> 'kvm_gmem_migrate_folio' is only used when CONFIG_MIGRATION
> is defined, And it will triggers the compiler warning about
> 'kvm_gmem_migrate_folio' defined but not used when CONFIG_MIGRATION
> isn't defined.
>
> The compiler complained like that:
> arch/x86/kvm/../../../virt/kvm/guest_memfd.c:262:12: error: ‘kvm_gmem_migrate_folio’ defined but not used [-Werror=unused-function]
> 262 | static int kvm_gmem_migrate_folio(struct address_space *mapping,
> | ^~~~~~~~~~~~~~~~~~~~~~
Already fixed, commit 80583d0cfd8f ("KVM: guest-memfd: fix unused-function warning")
in kvm/next.
https://lore.kernel.org/all/20231208184908.2298225-1-pbonzini@redhat.com
prev parent reply other threads:[~2023-12-11 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 3:05 [PATCH 1/1] KVM: Move kvm_gmem_migrate_folio inside CONFIG_MIGRATION 'Guanjun'
2023-12-11 15:15 ` Sean Christopherson [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=ZXcnlzDhcy8_CizZ@google.com \
--to=seanjc@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=guanjun@linux.alibaba.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tabba@google.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=yu.c.zhang@linux.intel.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.