From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernel test robot <lkp@intel.com>
Cc: John Ogness <john.ogness@linutronix.de>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [rt-devel:linux-5.16.y-rt-rebase 8/132] kernel/printk/printk.c:2628:2: error: implicit declaration of function 'boot_delay_msec'
Date: Wed, 26 Jan 2022 13:42:35 +0100 [thread overview]
Message-ID: <YfFBuyZstHF1zx+q@linutronix.de> (raw)
In-Reply-To: <202201220950.sysXbxm5-lkp@intel.com>
On 2022-01-22 09:13:20 [+0800], kernel test robot wrote:
…
> kernel/printk/printk.c: In function 'console_emit_next_record':
> >> kernel/printk/printk.c:2628:2: error: implicit declaration of function 'boot_delay_msec' [-Werror=implicit-function-declaration]
> 2628 | boot_delay_msec(r.info->level);
> | ^~~~~~~~~~~~~~~
> >> kernel/printk/printk.c:2629:2: error: implicit declaration of function 'printk_delay'; did you mean 'print_dev_t'? [-Werror=implicit-function-declaration]
> 2629 | printk_delay();
> | ^~~~~~~~~~~~
> | print_dev_t
> cc1: some warnings being treated as errors
I'm going to fold this in:
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 60c351afe7aa0..ae0cccf66b3cb 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -2265,6 +2265,8 @@ static void console_lock_spinning_enable(void) { }
static int console_lock_spinning_disable_and_check(void) { return 0; }
static void call_console_driver(struct console *con, const char *text, size_t len) {}
static bool suppress_message_printing(int level) { return false; }
+static inline void boot_delay_msec(int level) { }
+static inline void printk_delay(void) { }
#endif /* CONFIG_PRINTK */
Sebastian
next prev parent reply other threads:[~2022-01-26 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 1:13 kernel test robot
2022-01-26 12:42 ` Sebastian Andrzej Siewior [this message]
2022-01-22 1:54 kernel test robot
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=YfFBuyZstHF1zx+q@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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®