From: Hiroshi DOYU <hdoyu@nvidia.com>
To: <hdoyu@nvidia.com>
Cc: <linux-tegra@vger.kernel.org>, <kay@vrfy.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 1/1] printk: Make it compile with !CONFIG_PRINTK
Date: Mon, 14 May 2012 19:18:02 +0300 [thread overview]
Message-ID: <1337012284-18680-1-git-send-email-hdoyu@nvidia.com> (raw)
Add missing prepend_timestamp() dummy.
Signed-off-by: Hiroshi DOYU <hdoyu@nvidia.com>
---
kernel/printk.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/kernel/printk.c b/kernel/printk.c
index 8b027bd..5f9e278 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -1438,6 +1438,7 @@ EXPORT_SYMBOL(printk);
static struct log *log_from_idx(u32 idx) { return NULL; }
static u32 log_next(u32 idx) { return 0; }
static char *log_text(const struct log *msg) { return NULL; }
+static size_t prepend_timestamp(unsigned long long t, char *buf) { return 0; }
static void call_console_drivers(int level, const char *text, size_t len) {}
#endif /* CONFIG_PRINTK */
--
1.7.5.4
next reply other threads:[~2012-05-14 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 16:18 Hiroshi DOYU [this message]
2012-05-14 16:20 ` [PATCH 1/1] printk: Make it compile with !CONFIG_PRINTK Kay Sievers
2012-05-14 16:46 ` Joe Perches
2012-05-14 16:54 ` [PATCH 1/4] printk: Move to separate directory for easier modification Joe Perches
2012-05-14 16:54 ` [PATCH 2/4] printk: Separate out log_buf variables and functions Joe Perches
2012-05-14 16:54 ` [PATCH 3/4] printk: Separate out console bits to console.[ch] Joe Perches
2012-05-14 16:54 ` [PATCH 4/4] printk: Separate out kmsg bits to kmsg.c Joe Perches
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=1337012284-18680-1-git-send-email-hdoyu@nvidia.com \
--to=hdoyu@nvidia.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mingo@elte.hu \
/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