From: John Kacur <jkacur@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>,
John Kacur <jkacur@redhat.com>,
Clark Williams <williams@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH 1/2] Revert "rt: trivial fix to REMINDER block in init/main.c"
Date: Wed, 24 Mar 2010 18:35:06 +0100 [thread overview]
Message-ID: <1269452107-28655-2-git-send-email-jkacur@redhat.com> (raw)
In-Reply-To: <1269452107-28655-1-git-send-email-jkacur@redhat.com>
This reverts commit 3e39399ef4a742d994570488994be93ef17d4ef5.
CONFIG_STACK_TRACER really should not be in the reminder block.
By default it is not enabled, and has negligible impact.
Signed-off-by: John Kacur <jkacur@redhat.com>
---
init/main.c | 3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/init/main.c b/init/main.c
index 48393c0..aa48b7b 100644
--- a/init/main.c
+++ b/init/main.c
@@ -928,9 +928,6 @@ static int __init kernel_init(void * unused)
#ifdef CONFIG_PREEMPT_TRACER
printk(KERN_ERR "* CONFIG_PREEMPT_TRACER *\n");
#endif
-#ifdef CONFIG_STACK_TRACER
- printk(KERN_ERR "* CONFIG_STACK_TRACER *\n");
-#endif
#if defined(CONFIG_FTRACE) && !defined(CONFIG_FTRACE_MCOUNT_RECORD)
printk(KERN_ERR "* CONFIG_FTRACE *\n");
#endif
--
1.6.6.1
next prev parent reply other threads:[~2010-03-24 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 17:35 [PATCH 0/2] [rt-kernel] John Kacur
2010-03-24 17:35 ` John Kacur [this message]
2010-03-24 18:13 ` [PATCH 1/2] Revert "rt: trivial fix to REMINDER block in init/main.c" Steven Rostedt
2010-03-24 17:35 ` [PATCH 2/2] rt: Remove CONFIG_STACK_TRACER from DEBUG_COUNT John Kacur
2010-03-24 18:13 ` Steven Rostedt
2010-03-24 19:27 ` John Kacur
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=1269452107-28655-2-git-send-email-jkacur@redhat.com \
--to=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).