public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: [PATCH] kvm-kmod: Fix tracepoint warnings against OpenSUSE's 2.6.27
Date: Thu, 25 Jun 2009 14:47:15 +0200	[thread overview]
Message-ID: <4A4371D3.2010605@siemens.com> (raw)

OpenSUSE's 2.6.27 already includes tracepoints and generates a lot of
warnings regarding redefinition of tracepoint_synchronize_unregister.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---

 external-module-compat-comm.h |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/external-module-compat-comm.h b/external-module-compat-comm.h
index c0ae66c..c681dd3 100644
--- a/external-module-compat-comm.h
+++ b/external-module-compat-comm.h
@@ -841,7 +841,7 @@ static inline struct file *eventfd_fget(int fd)
 
 #endif
 
-/* tracepoints were introduced in 2.6.29, but changed in 2.6.30 */
+/* tracepoints were introduced in 2.6.28, but changed in 2.6.30 */
 
 #include <linux/tracepoint.h>
 
@@ -884,6 +884,7 @@ struct tracepoint;
 #define TRACE_EVENT(name, proto, args, struct, assign, print)	\
 	DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
 
+#undef tracepoint_synchronize_unregister
 #define tracepoint_synchronize_unregister() do {} while (0)
 
 #endif

             reply	other threads:[~2009-06-25 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 12:47 Jan Kiszka [this message]
2009-06-28  7:55 ` [PATCH] kvm-kmod: Fix tracepoint warnings against OpenSUSE's 2.6.27 Avi Kivity

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=4A4371D3.2010605@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.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