KVM: fix "Should it be static?" warnings from sparse
authorFengguang Wu <fengguang.wu@intel.com>
Mon, 19 Jan 2015 14:33:39 +0000 (22:33 +0800)
committerPaolo Bonzini <pbonzini@redhat.com>
Tue, 20 Jan 2015 19:38:35 +0000 (20:38 +0100)
commit69b0049a89ad418cd68aa59e7f1e6619a04a4a6f
treefbfaae21814d391c4ed6ad89574f717dd470c117
parentd91ffee9ec633c6523ef1ea39c36ace578760258
KVM: fix "Should it be static?" warnings from sparse

arch/x86/kvm/x86.c:495:5: sparse: symbol 'kvm_read_nested_guest_page' was not declared. Should it be static?
arch/x86/kvm/x86.c:646:5: sparse: symbol '__kvm_set_xcr' was not declared. Should it be static?
arch/x86/kvm/x86.c:1183:15: sparse: symbol 'max_tsc_khz' was not declared. Should it be static?
arch/x86/kvm/x86.c:1237:6: sparse: symbol 'kvm_track_tsc_matching' was not declared. Should it be static?

Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
arch/x86/kvm/x86.c