From: Jan Altenberg <tb10alj@tglx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] 2.6.16-rc6-rt9 - Remove duplicated REMINDER prints
Date: Fri, 17 Mar 2006 15:05:35 +0100 [thread overview]
Message-ID: <441AC22F.4090007@tglx.de> (raw)
Hi,
looking at init/main.c, I recognized duplicated REMINDER prints.
(existant since 2.6.16-rc6-rt1)
See attached patch against 2.6.16-rc6-rt9
Signed-off-by: Jan Altenberg <tb10alj@tglx.de>
----------------------
--- linux-2.6.16-rc6-rt9/init/main.c.orig 2006-03-17 14:50:28.000000000 +0100
+++ linux-2.6.16-rc6-rt9/init/main.c 2006-03-17 14:52:06.000000000 +0100
@@ -714,47 +714,6 @@ static int init(void * unused)
do_basic_setup();
-#define DEBUG_COUNT (defined(CONFIG_DEBUG_RT_MUTEXES) + defined(CONFIG_DEBUG_PREEMPT) + defined(CONFIG_CRITICAL_PREEMPT_TIMING) + defined(CONFIG_CRITICAL_IRQSOFF_TIMING) + defined(CONFIG_LATENCY_TRACE) + defined(CONFIG_DEBUG_SLAB) + defined(CONFIG_DEBUG_PAGEALLOC))
-
-#if DEBUG_COUNT > 0
- printk(KERN_ERR "*****************************************************************************\n");
- printk(KERN_ERR "* *\n");
-#if DEBUG_COUNT == 1
- printk(KERN_ERR "* REMINDER, the following debugging option is turned on in your .config: *\n");
-#else
- printk(KERN_ERR "* REMINDER, the following debugging options are turned on in your .config: *\n");
-#endif
- printk(KERN_ERR "* *\n");
-#ifdef CONFIG_DEBUG_RT_MUTEXES
- printk(KERN_ERR "* CONFIG_DEBUG_RT_MUTEXES *\n");
-#endif
-#ifdef CONFIG_DEBUG_PREEMPT
- printk(KERN_ERR "* CONFIG_DEBUG_PREEMPT *\n");
-#endif
-#ifdef CONFIG_CRITICAL_PREEMPT_TIMING
- printk(KERN_ERR "* CONFIG_CRITICAL_PREEMPT_TIMING *\n");
-#endif
-#ifdef CONFIG_CRITICAL_IRQSOFF_TIMING
- printk(KERN_ERR "* CONFIG_CRITICAL_IRQSOFF_TIMING *\n");
-#endif
-#ifdef CONFIG_LATENCY_TRACE
- printk(KERN_ERR "* CONFIG_LATENCY_TRACE *\n");
-#endif
-#ifdef CONFIG_DEBUG_SLAB
- printk(KERN_ERR "* CONFIG_DEBUG_SLAB *\n");
-#endif
-#ifdef CONFIG_DEBUG_PAGEALLOC
- printk(KERN_ERR "* CONFIG_DEBUG_PAGEALLOC *\n");
-#endif
- printk(KERN_ERR "* *\n");
-#if DEBUG_COUNT == 1
- printk(KERN_ERR "* it may increase runtime overhead and latencies. *\n");
-#else
- printk(KERN_ERR "* they may increase runtime overhead and latencies. *\n");
-#endif
- printk(KERN_ERR "* *\n");
- printk(KERN_ERR "*****************************************************************************\n");
-#endif
/*
* check if there is an early userspace init. If yes, let it do all
* the work
reply other threads:[~2006-03-17 14:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=441AC22F.4090007@tglx.de \
--to=tb10alj@tglx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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