From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Petr Mladek <pmladek@suse.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Maninder Singh <maninder1.s@samsung.com>
Subject: linux-next: build warning after merge of the printk tree
Date: Tue, 10 Jul 2018 16:45:14 +1000 [thread overview]
Message-ID: <20180710164514.22c552db@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
Hi all,
After merging the printk tree, today's linux-next build (x86_64
allnoconfig) produced this warning:
kernel/printk/printk.c:2033:13: warning: 'suppress_message_printing' defined but not used [-Wunused-function]
static bool suppress_message_printing(int level) { return false; }
^~~~~~~~~~~~~~~~~~~~~~~~~
Introduced by commit
375899cddcbb ("printk: make sure to print log on console.")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-07-10 6:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180710064527epcas1p16fd9ad765711d69264b3251890bbcc2e@epcms5p5>
2018-07-10 6:45 ` Stephen Rothwell [this message]
2018-07-10 7:16 ` linux-next: build warning after merge of the printk tree Maninder Singh
2018-07-10 9:19 ` Petr Mladek
2018-07-10 11:53 ` [PATCH] printk: Fix warning about unused suppress_message_printing kbuild test robot
2018-07-10 13:15 ` linux-next: build warning after merge of the printk tree Sergey Senozhatsky
2021-07-20 6:24 Stephen Rothwell
2021-07-20 12:18 ` Chris Down
2021-07-20 12:22 ` Chris Down
2021-07-25 21:16 ` Jonathan Corbet
2021-07-26 12:28 ` Petr Mladek
2021-07-26 13:07 ` Chris Down
-- strict thread matches above, loose matches on Subject: below --
2022-11-22 7:10 Stephen Rothwell
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=20180710164514.22c552db@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=pmladek@suse.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