From: tip-bot for Frederic Weisbecker <fweisbec@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
fweisbec@gmail.com, peterz@infradead.org, sfr@canb.auug.org.au,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:perf/core] hw-breakpoints: Fix unused function in off-case
Date: Thu, 26 Nov 2009 09:56:23 GMT [thread overview]
Message-ID: <tip-80bbf6b641c8843b9d751a1f299aa7ee073ab9d4@git.kernel.org> (raw)
In-Reply-To: <1259180453-5813-1-git-send-email-fweisbec@gmail.com>
Commit-ID: 80bbf6b641c8843b9d751a1f299aa7ee073ab9d4
Gitweb: http://git.kernel.org/tip/80bbf6b641c8843b9d751a1f299aa7ee073ab9d4
Author: Frederic Weisbecker <fweisbec@gmail.com>
AuthorDate: Wed, 25 Nov 2009 21:20:53 +0100
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Thu, 26 Nov 2009 10:40:51 +0100
hw-breakpoints: Fix unused function in off-case
bp_perf_event_destroy() is unused in its off-case version, let's
remove it to fix the following warning reported by Stephen
Rothwell in linux-next:
kernel/perf_event.c:4306: warning: 'bp_perf_event_destroy' defined but not used
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>
LKML-Reference: <1259180453-5813-1-git-send-email-fweisbec@gmail.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/perf_event.c | 4 ----
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/kernel/perf_event.c b/kernel/perf_event.c
index 34a1b9d..f8c7939 100644
--- a/kernel/perf_event.c
+++ b/kernel/perf_event.c
@@ -4303,10 +4303,6 @@ void perf_bp_event(struct perf_event *bp, void *data)
perf_swevent_add(bp, 1, 1, &sample, regs);
}
#else
-static void bp_perf_event_destroy(struct perf_event *event)
-{
-}
-
static const struct pmu *bp_perf_event_init(struct perf_event *bp)
{
return NULL;
prev parent reply other threads:[~2009-11-26 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 10:53 linux-next: tip tree build warning Stephen Rothwell
2009-11-25 12:28 ` Frederic Weisbecker
2009-11-25 20:20 ` [PATCH] hw-breakpoints: Fix unused function in off-case Frederic Weisbecker
2009-11-26 9:56 ` tip-bot for Frederic Weisbecker [this message]
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=tip-80bbf6b641c8843b9d751a1f299aa7ee073ab9d4@git.kernel.org \
--to=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.