From: Will Deacon <will.deacon@arm.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] locking/lockdep: remove print_lock_trace function
Date: Fri, 24 May 2019 19:44:31 +0100 [thread overview]
Message-ID: <20190524184431.GF9697@fuggles.cambridge.arm.com> (raw)
In-Reply-To: <20190516191326.27003-1-anders.roxell@linaro.org>
On Thu, May 16, 2019 at 09:13:26PM +0200, Anders Roxell wrote:
> 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]
> static void print_lock_trace(struct lock_trace *trace, unsigned int
> spaces)
>
> Rework so we remove the function if CONFIG_PROVE_LOCKING isn't set.
>
> Fixes: c120bce78065 ("lockdep: Simplify stack trace handling")
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> kernel/locking/lockdep.c | 4 ----
> 1 file changed, 4 deletions(-)
Acked-by: Will Deacon <will.deacon@arm.com>
Will
prev parent reply other threads:[~2019-05-24 18:44 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:locking/core] locking/lockdep: Remove the unused print_lock_trace() function tip-bot for Anders Roxell
2019-05-24 18:44 ` Will Deacon [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=20190524184431.GF9697@fuggles.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=anders.roxell@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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