All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH] KVM: CPUID: kvm_supported_xss() can be static
Date: Thu, 13 Feb 2020 18:09:29 +0800	[thread overview]
Message-ID: <20200213100925.GA28399@9560152b1213> (raw)
In-Reply-To: <20200211065706.3462-1-weijiang.yang@intel.com>

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]


Fixes: c0a25f0ace60 ("KVM: CPUID: Enable supervisor XSAVE states in CPUID enumeration and XSS")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
 cpuid.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
index 0f42df82e9a0f..04f80b3ec18a3 100644
--- a/arch/x86/kvm/cpuid.c
+++ b/arch/x86/kvm/cpuid.c
@@ -63,7 +63,7 @@ u64 kvm_supported_xcr0(void)
 }
 
 extern int host_xss;
-u64 kvm_supported_xss(void)
+static u64 kvm_supported_xss(void)
 {
 	return KVM_SUPPORTED_XSS & host_xss;
 }

  parent reply	other threads:[~2020-02-13 10:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11  6:57 [RFC PATCH 1/2] KVM: CPUID: Enable supervisor XSAVE states in CPUID enumeration and XSS Yang Weijiang
2020-02-11  6:57 ` [RFC PATCH 2/2] KVM: tests: Selftest for xsave CPUID enumeration Yang Weijiang
2020-02-13 10:09 ` [RFC PATCH 1/2] KVM: CPUID: Enable supervisor XSAVE states in CPUID enumeration and XSS kbuild test robot
2020-02-13 10:09 ` kbuild test robot [this message]
2020-02-17  4:26 ` Xiaoyao Li
2020-02-17 13:03   ` Yang Weijiang
2020-02-17 13:20     ` Xiaoyao Li
2020-02-18  5:44       ` Xiaoyao Li
2020-02-18 12:46         ` Yang Weijiang
2020-02-18 12:43       ` Yang Weijiang

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=20200213100925.GA28399@9560152b1213 \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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.