From: tip-bot for Anders Roxell <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
peterz@infradead.org, tglx@linutronix.de, mingo@kernel.org,
anders.roxell@linaro.org, hpa@zytor.com
Subject: [tip:locking/core] locking/lockdep: Remove the unused print_lock_trace() function
Date: Fri, 24 May 2019 01:10:58 -0700 [thread overview]
Message-ID: <tip-c0090c4c85c27d1fa3d785c935501b7207cd2869@git.kernel.org> (raw)
In-Reply-To: <20190516191326.27003-1-anders.roxell@linaro.org>
Commit-ID: c0090c4c85c27d1fa3d785c935501b7207cd2869
Gitweb: https://git.kernel.org/tip/c0090c4c85c27d1fa3d785c935501b7207cd2869
Author: Anders Roxell <anders.roxell@linaro.org>
AuthorDate: Thu, 16 May 2019 21:13:26 +0200
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Fri, 24 May 2019 09:05:46 +0200
locking/lockdep: Remove the unused print_lock_trace() function
gcc warns that function print_lock_trace() is unused if
CONFIG_PROVE_LOCKING isn't set:
../kernel/locking/lockdep.c:2820:13: warning: ‘print_lock_trace’ defined but not used [-Wunused-function]
Rework so we remove the function if CONFIG_PROVE_LOCKING isn't set.
Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: will.deacon@arm.com
Fixes: c120bce78065 ("lockdep: Simplify stack trace handling")
Link: http://lkml.kernel.org/r/20190516191326.27003-1-anders.roxell@linaro.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/locking/lockdep.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
index 6b283b4f87aa..8d32ae7768a7 100644
--- a/kernel/locking/lockdep.c
+++ b/kernel/locking/lockdep.c
@@ -2818,10 +2818,6 @@ static inline int validate_chain(struct task_struct *curr,
{
return 1;
}
-
-static void print_lock_trace(struct lock_trace *trace, unsigned int spaces)
-{
-}
#endif
/*
next prev parent reply other threads:[~2019-05-24 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 19:13 [PATCH] locking/lockdep: remove print_lock_trace function Anders Roxell
2019-05-24 8:10 ` tip-bot for Anders Roxell [this message]
2019-05-24 18:44 ` Will Deacon
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-c0090c4c85c27d1fa3d785c935501b7207cd2869@git.kernel.org \
--to=tipbot@zytor.com \
--cc=anders.roxell@linaro.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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