From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Kay Sievers <kay@vrfy.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH -next] printk: add stub for prepend_timestamp()
Date: Fri, 11 May 2012 16:36:07 -0700 [thread overview]
Message-ID: <4FADA267.1020608@xenotime.net> (raw)
In-Reply-To: <4FAD9E94.7020109@xenotime.net>
From: Randy Dunlap <rdunlap@xenotime.net>
Add a stub for prepend_timestamp() when CONFIG_PRINTK is not
enabled. Fixes this build error:
kernel/printk.c:1770:3: error: implicit declaration of function 'prepend_timestamp'
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
kernel/printk.c | 4 ++++
1 file changed, 4 insertions(+)
--- linux-next-20120511.orig/kernel/printk.c
+++ linux-next-20120511/kernel/printk.c
@@ -1439,6 +1439,10 @@ static struct log *log_from_idx(u32 idx)
static u32 log_next(u32 idx) { return 0; }
static char *log_text(const struct log *msg) { return NULL; }
static void call_console_drivers(int level, const char *text, size_t len) {}
+static size_t prepend_timestamp(unsigned long long t, char *buf)
+{
+ return 0;
+}
#endif /* CONFIG_PRINTK */
next prev parent reply other threads:[~2012-05-11 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 6:27 linux-next: Tree for May 11 Stephen Rothwell
2012-05-11 23:19 ` linux-next: Tree for May 11 (printk) Randy Dunlap
2012-05-11 23:36 ` Randy Dunlap [this message]
2012-05-11 23:37 ` [PATCH -next] via_wdt: depends on PCI Randy Dunlap
2012-05-14 13:14 ` Wim Van Sebroeck
2012-05-11 23:52 ` linux-next: Tree for May 11 (perf_event_amd.c) Randy Dunlap
2012-05-12 1:33 ` [PATCH -next] watchdog: fix ie6xx_wdt.c printk format warning Randy Dunlap
2012-05-14 13:15 ` Wim Van Sebroeck
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=4FADA267.1020608@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=gregkh@linuxfoundation.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.