From: tip-bot for Andrew Morton <akpm@linux-foundation.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
a.p.zijlstra@chello.nl, torvalds@linux-foundation.org,
benh@kernel.crashing.org, akpm@linux-foundation.org,
stable@kernel.org, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:core/locking] kernel/mutex.c: Fix unused var warning
Date: Tue, 18 May 2010 14:48:43 GMT [thread overview]
Message-ID: <tip-0f14452563e342637f9a3a2f036cac7315081b2b@git.kernel.org> (raw)
In-Reply-To: <201005141841.o4EIfcl0015387@imap1.linux-foundation.org>
Commit-ID: 0f14452563e342637f9a3a2f036cac7315081b2b
Gitweb: http://git.kernel.org/tip/0f14452563e342637f9a3a2f036cac7315081b2b
Author: Andrew Morton <akpm@linux-foundation.org>
AuthorDate: Fri, 14 May 2010 11:13:48 -0700
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Tue, 18 May 2010 16:46:03 +0200
kernel/mutex.c: Fix unused var warning
kernel/mutex.c: In function '__mutex_lock_common':
kernel/mutex.c:148: warning: unused variable 'timeout'
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
LKML-Reference: <201005141841.o4EIfcl0015387@imap1.linux-foundation.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/mutex.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/mutex.c b/kernel/mutex.c
index 7d4626b..b998c6e 100644
--- a/kernel/mutex.c
+++ b/kernel/mutex.c
@@ -145,7 +145,7 @@ __mutex_lock_common(struct mutex *lock, long state, unsigned int subclass,
struct task_struct *task = current;
struct mutex_waiter waiter;
unsigned long flags;
- unsigned long timeout;
+ unsigned long timeout __maybe_unused;
preempt_disable();
mutex_acquire(&lock->dep_map, subclass, 0, ip);
parent reply other threads:[~2010-05-18 14:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201005141841.o4EIfcl0015387@imap1.linux-foundation.org>]
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-0f14452563e342637f9a3a2f036cac7315081b2b@git.kernel.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=benh@kernel.crashing.org \
--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=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).