mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Simon Holm Thøgersen" <odie@cs.aau.dk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] x86/paravirt: fix compile warning for !SMP builds
Date: Tue, 14 Oct 2008 00:59:26 +0200	[thread overview]
Message-ID: <1223938766.21717.17.camel@odie.local> (raw)

This fixes the following compile warning for !SMP builds:

arch/x86/kernel/paravirt-spinlocks.c:11: warning: 'default_spin_lock_flags' defined but not used

that was introduced by 63d3a75d (x86/paravirt: add spin_lock_flags lock op).

Signed-off-by: Simon Holm Thøgersen <odie@cs.aau.dk>
---
 arch/x86/kernel/paravirt-spinlocks.c |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kernel/paravirt-spinlocks.c b/arch/x86/kernel/paravirt-spinlocks.c
index 0e9f198..ebcb33d 100644
--- a/arch/x86/kernel/paravirt-spinlocks.c
+++ b/arch/x86/kernel/paravirt-spinlocks.c
@@ -7,13 +7,13 @@
 
 #include <asm/paravirt.h>
 
+#ifdef CONFIG_SMP
 static void default_spin_lock_flags(struct raw_spinlock *lock, unsigned long flags)
 {
 	__raw_spin_lock(lock);
 }
 
 struct pv_lock_ops pv_lock_ops = {
-#ifdef CONFIG_SMP
 	.spin_is_locked = __ticket_spin_is_locked,
 	.spin_is_contended = __ticket_spin_is_contended,
 
@@ -21,8 +21,10 @@ struct pv_lock_ops pv_lock_ops = {
 	.spin_lock_flags = default_spin_lock_flags,
 	.spin_trylock = __ticket_spin_trylock,
 	.spin_unlock = __ticket_spin_unlock,
-#endif
 };
+#else
+struct pv_lock_ops pv_lock_ops;
+#endif
 EXPORT_SYMBOL(pv_lock_ops);
 
 void __init paravirt_use_bytelocks(void)
-- 
1.5.6.2.255.gbed62


                 reply	other threads:[~2008-10-13 23:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1223938766.21717.17.camel@odie.local \
    --to=odie@cs.aau.dk \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®