From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Frederic Weisbecker <fweisbec@gmail.com>, Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] hw-breakpoints: let modify_user_hw_breakpoint return an int
Date: Mon, 14 Dec 2009 10:24:12 +0100 [thread overview]
Message-ID: <20091214092412.GA5242@osiris.boeblingen.de.ibm.com> (raw)
From: Heiko Carstens <heiko.carstens@de.ibm.com>
Let modify_user_hw_breakpoint return an int to avoid hundreds of compile
warnings like this one:
include/linux/hw_breakpoint.h: In function 'modify_user_hw_breakpoint':
include/linux/hw_breakpoint.h:96: warning: return makes integer from pointer without a cast
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
---
include/linux/hw_breakpoint.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/include/linux/hw_breakpoint.h
===================================================================
--- linux-2.6.orig/include/linux/hw_breakpoint.h
+++ linux-2.6/include/linux/hw_breakpoint.h
@@ -93,7 +93,7 @@ register_user_hw_breakpoint(struct perf_
struct task_struct *tsk) { return NULL; }
static inline int
modify_user_hw_breakpoint(struct perf_event *bp,
- struct perf_event_attr *attr) { return NULL; }
+ struct perf_event_attr *attr) { return 0; }
static inline struct perf_event *
register_wide_hw_breakpoint_cpu(struct perf_event_attr *attr,
perf_overflow_handler_t triggered,
next reply other threads:[~2009-12-14 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 9:24 Heiko Carstens [this message]
2009-12-14 9:49 ` [tip:perf/urgent] hw-breakpoints: Let modify_user_hw_breakpoint() " tip-bot for Heiko Carstens
2009-12-14 10:37 ` Frederic Weisbecker
2009-12-14 10:38 ` Stephen Rothwell
2009-12-14 10:54 ` Ingo Molnar
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=20091214092412.GA5242@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=fweisbec@gmail.com \
--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®