From: tip-bot for Ingo Molnar <mingo@elte.hu>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
penberg@cs.helsinki.fi, lizf@cn.fujitsu.com, tglx@linutronix.de,
mingo@elte.hu
Subject: [tip:perf/urgent] perf kmem: Fix unused argument build warning
Date: Thu, 10 Dec 2009 07:51:56 GMT [thread overview]
Message-ID: <tip-7931241694b25589658b1ceb02218d2750540ae0@git.kernel.org> (raw)
In-Reply-To: <4B20A195.8030106@cn.fujitsu.com>
Commit-ID: 7931241694b25589658b1ceb02218d2750540ae0
Gitweb: http://git.kernel.org/tip/7931241694b25589658b1ceb02218d2750540ae0
Author: Ingo Molnar <mingo@elte.hu>
AuthorDate: Thu, 10 Dec 2009 08:43:34 +0100
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Thu, 10 Dec 2009 08:44:39 +0100
perf kmem: Fix unused argument build warning
Fix:
builtin-kmem.c: In function 'parse_caller_opt':
builtin-kmem.c:690: error: unused parameter 'arg'
builtin-kmem.c: In function 'parse_alloc_opt':
builtin-kmem.c:697: error: unused parameter 'arg'
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>
LKML-Reference: <4B20A195.8030106@cn.fujitsu.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
tools/perf/builtin-kmem.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/builtin-kmem.c b/tools/perf/builtin-kmem.c
index 1b04787..5f20951 100644
--- a/tools/perf/builtin-kmem.c
+++ b/tools/perf/builtin-kmem.c
@@ -687,14 +687,14 @@ static int parse_sort_opt(const struct option *opt __used,
}
static int parse_caller_opt(const struct option *opt __used,
- const char *arg, int unset __used)
+ const char *arg __used, int unset __used)
{
caller_flag = (alloc_flag + 1);
return 0;
}
static int parse_alloc_opt(const struct option *opt __used,
- const char *arg, int unset __used)
+ const char *arg __used, int unset __used)
{
alloc_flag = (caller_flag + 1);
return 0;
prev parent reply other threads:[~2009-12-10 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 7:21 [PATCH 1/2] perf kmem: Show usage if no option is specified Li Zefan
2009-12-10 7:22 ` [PATCH 2/2] perf tools: Align long options which have no short forms Li Zefan
2009-12-10 7:51 ` [tip:perf/urgent] " tip-bot for Li Zefan
2009-12-10 7:23 ` [PATCH 1/2] perf kmem: Show usage if no option is specified Pekka Enberg
2009-12-10 7:30 ` Ingo Molnar
2009-12-10 7:50 ` [tip:perf/urgent] " tip-bot for Li Zefan
2009-12-10 7:51 ` tip-bot for Ingo Molnar [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-7931241694b25589658b1ceb02218d2750540ae0@git.kernel.org \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@redhat.com \
--cc=penberg@cs.helsinki.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome