From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: <x86@kernel.org>, Jiri Kosina <trivial@kernel.org>
Cc: <mingo@redhat.com>, <hpa@zytor.com>, <gleb@redhat.com>,
<pbonzini@redhat.com>, <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Subject: [PATCH trivial sparse fix] guest x86 kvm: fix sparse warning: symbol 'klock_waiting' was not declared. Should it be static
Date: Fri, 16 Aug 2013 15:08:41 +0530 [thread overview]
Message-ID: <1376645921-8056-1-git-send-email-raghavendra.kt@linux.vnet.ibm.com> (raw)
In-Reply-To: <y>
It was not declared as static since it was thought to be used by pv-flushtlb earlier.
Signed-off-by: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
---
This should apply on top of tip/spinlocks and fixes the sparse warning
introduced by pvspinlock patch series.
arch/x86/kernel/kvm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c
index b8ef630..56e2fa4 100644
--- a/arch/x86/kernel/kvm.c
+++ b/arch/x86/kernel/kvm.c
@@ -529,7 +529,7 @@ arch_initcall(activate_jump_labels);
#ifdef CONFIG_PARAVIRT_SPINLOCKS
/* Kick a cpu by its apicid. Used to wake up a halted vcpu */
-void kvm_kick_cpu(int cpu)
+static void kvm_kick_cpu(int cpu)
{
int apicid;
unsigned long flags = 0;
--
1.7.11.7
next reply other threads:[~2013-08-16 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 9:38 Raghavendra K T [this message]
2013-08-19 9:55 ` [tip:x86/spinlocks] x86/kvm/guest: Fix sparse warning: "symbol ' klock_waiting' was not declared as static" tip-bot for Raghavendra K T
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=1376645921-8056-1-git-send-email-raghavendra.kt@linux.vnet.ibm.com \
--to=raghavendra.kt@linux.vnet.ibm.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=trivial@kernel.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®