From: Peter Zijlstra <peterz@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH] printk: Make it compile with !CONFIG_PRINTK
Date: Thu, 15 Mar 2012 12:35:37 +0100 [thread overview]
Message-ID: <1331811337.18960.179.camel@twins> (raw)
In-Reply-To: <20120315071934.77f0af64a4c633c545d68ea4@canb.auug.org.au>
On Thu, 2012-03-15 at 07:19 +1100, Stephen Rothwell wrote:
> On Wed, 14 Mar 2012 08:56:22 -0700 Randy Dunlap <rdunlap@xenotime.net> wrote:
> >
> > on x86_64:
> >
> > kernel/printk.c:1230:5: error: redefinition of 'printk_sched'
> > include/linux/printk.h:136:5: note: previous definition of 'printk_sched' was here
>
> Caused by commit 3ccf3e830615 ("printk/sched: Introduce special
> printk_sched() for those awkward moments") from the tip tree. The
> declaration in include/linux/printk.h has alternatives determined by
> CONFIG_PRINTK, but the definition in kernel/printk.c is not so
> protected ...
Ingo, could you stick this on top.. ?
---
Subject: printk: Make it compile with !CONFIG_PRINTK
Commit 3ccf3e830615 ("printk/sched: Introduce special printk_sched() for
those awkward moments") overlooked an #ifdef, so move code around to
respect these directives.
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
kernel/printk.c | 40 ++++++++++++++++++++--------------------
1 files changed, 20 insertions(+), 20 deletions(-)
diff --git a/kernel/printk.c b/kernel/printk.c
index 8b6981e..b663c2c 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -1227,26 +1227,6 @@ int is_console_locked(void)
static DEFINE_PER_CPU(int, printk_pending);
static DEFINE_PER_CPU(char [PRINTK_BUF_SIZE], printk_sched_buf);
-int printk_sched(const char *fmt, ...)
-{
- unsigned long flags;
- va_list args;
- char *buf;
- int r;
-
- local_irq_save(flags);
- buf = __get_cpu_var(printk_sched_buf);
-
- va_start(args, fmt);
- r = vsnprintf(buf, PRINTK_BUF_SIZE, fmt, args);
- va_end(args);
-
- __this_cpu_or(printk_pending, PRINTK_PENDING_SCHED);
- local_irq_restore(flags);
-
- return r;
-}
-
void printk_tick(void)
{
if (__this_cpu_read(printk_pending)) {
@@ -1663,6 +1643,26 @@ late_initcall(printk_late_init);
#if defined CONFIG_PRINTK
+int printk_sched(const char *fmt, ...)
+{
+ unsigned long flags;
+ va_list args;
+ char *buf;
+ int r;
+
+ local_irq_save(flags);
+ buf = __get_cpu_var(printk_sched_buf);
+
+ va_start(args, fmt);
+ r = vsnprintf(buf, PRINTK_BUF_SIZE, fmt, args);
+ va_end(args);
+
+ __this_cpu_or(printk_pending, PRINTK_PENDING_SCHED);
+ local_irq_restore(flags);
+
+ return r;
+}
+
/*
* printk rate limiting, lifted from the networking subsystem.
*
next prev parent reply other threads:[~2012-03-15 11:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 7:19 linux-next: Tree for Mar 14 Stephen Rothwell
2012-03-14 15:56 ` linux-next: Tree for Mar 14 (printk) Randy Dunlap
2012-03-14 20:19 ` Stephen Rothwell
2012-03-15 11:35 ` Peter Zijlstra [this message]
2012-03-15 15:44 ` [PATCH] printk: Make it compile with !CONFIG_PRINTK Randy Dunlap
2012-03-14 17:02 ` [PATCH -next] staging: ozwpan depends on NET Randy Dunlap
2012-03-14 17:10 ` Chris Kelly
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=1331811337.18960.179.camel@twins \
--to=peterz@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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