From: tip-bot for Mengting Zhang <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: alexander.sverdlin@gmail.com, torvalds@linux-foundation.org,
hpa@zytor.com, alexander.levin@verizon.com, mingo@kernel.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
peterz@infradead.org, zhangmengting@huawei.com
Subject: [tip:locking/urgent] tools/lib/lockdep: Add missing declaration of 'pr_cont()'
Date: Wed, 13 Dec 2017 02:22:26 -0800 [thread overview]
Message-ID: <tip-92ccc262e485781ff4c0fb3b7c77a619282df49a@git.kernel.org> (raw)
In-Reply-To: <20171212181644.11913-2-alexander.levin@verizon.com>
Commit-ID: 92ccc262e485781ff4c0fb3b7c77a619282df49a
Gitweb: https://git.kernel.org/tip/92ccc262e485781ff4c0fb3b7c77a619282df49a
Author: Mengting Zhang <zhangmengting@huawei.com>
AuthorDate: Tue, 12 Dec 2017 18:16:57 +0000
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 13 Dec 2017 11:17:35 +0100
tools/lib/lockdep: Add missing declaration of 'pr_cont()'
Commit:
681fbec881de ("lockdep: Use consistent printing primitives")
has moved lockdep away from using printk() for printing.
The commit added usage of pr_cont() which wasn't wrapped in the
userspace headers, causing the following warning for the
liblockdep build:
../../../kernel/locking/lockdep.c:3544:2: warning: implicit declaration of function 'pr_cont' [-Wimplicit-function-declaration]
Adding an empty declaration of 'pr_cont' fixes the problem.
Signed-off-by: Mengting Zhang <zhangmengting@huawei.com>
Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
Reviewed-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: a.p.zijlstra@chello.nl
Link: http://lkml.kernel.org/r/20171212181644.11913-2-alexander.levin@verizon.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
tools/include/linux/lockdep.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/include/linux/lockdep.h b/tools/include/linux/lockdep.h
index 940c1b0..6b0c36a 100644
--- a/tools/include/linux/lockdep.h
+++ b/tools/include/linux/lockdep.h
@@ -48,6 +48,7 @@ static inline int debug_locks_off(void)
#define printk(...) dprintf(STDOUT_FILENO, __VA_ARGS__)
#define pr_err(format, ...) fprintf (stderr, format, ## __VA_ARGS__)
#define pr_warn pr_err
+#define pr_cont pr_err
#define list_del_rcu list_del
next prev parent reply other threads:[~2017-12-13 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 18:16 [GIT PULL 0/2] tools/lib/lockdep: fixes for v4.15 alexander.levin
2017-12-12 18:16 ` [PATCH 1/2] tools/lib/lockdep: Add missing declaration of 'pr_cont()' alexander.levin
2017-12-13 10:22 ` tip-bot for Mengting Zhang [this message]
2017-12-12 18:16 ` [PATCH 2/2] tools/lib/lockdep: add empty declaration for early_param alexander.levin
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-92ccc262e485781ff4c0fb3b7c77a619282df49a@git.kernel.org \
--to=tipbot@zytor.com \
--cc=alexander.levin@verizon.com \
--cc=alexander.sverdlin@gmail.com \
--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 \
--cc=zhangmengting@huawei.com \
/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
all inboxes | Powered by JetHome®