From: John Kacur <jkacur@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
rt-users <linux-rt-users@vger.kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>
Subject: [rt: PATCH - resend] Fix-up boot-up warnings surrounding CONFIG_STACK_TRACER
Date: Wed, 7 Apr 2010 20:40:39 +0200 [thread overview]
Message-ID: <1270665640-8520-1-git-send-email-jkacur@redhat.com> (raw)
Thomas
I respun this against 2.6.33.2-rt13 and combined the two original patches
into one as suggested by Steven Rostedt, and added his Acked-by.
Please consider this patch for the next -rt release.
Thanks
John Kacur (1):
rt: This fixes the boot-up messages related to CONFIG_STACK_TRACER
init/main.c | 5 +----
1 files changed, 1 insertions(+), 4 deletions(-)
next reply other threads:[~2010-04-07 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 18:40 John Kacur [this message]
2010-04-07 18:40 ` [PATCH] rt: This fixes the boot-up messages related to CONFIG_STACK_TRACER 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=1270665640-8520-1-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).