From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Qiang Huang <h.huangqiang@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
stable-rt@vger.kernel.org
Subject: Re: [PATCH] sched: fix the wrong macro name of CONFIG_DEBUG_PREEMPT
Date: Thu, 25 Apr 2013 18:35:34 +0200 [thread overview]
Message-ID: <20130425163534.GE5561@linutronix.de> (raw)
In-Reply-To: <1365518245.25498.57.camel@gandalf.local.home>
* Steven Rostedt | 2013-04-09 10:37:25 [-0400]:
>Thomas,
>
>Can you pick up this patch for 3.8-rt? I'll add it to stable after you
>have done so.
>
>Thanks,
>
>-- Steve
>
>On Mon, 2013-04-08 at 19:47 +0800, Qiang Huang wrote:
>> Might be a typo, would cause some debug code never be run.
Looks like a type, indeed. Applied.
Sebastian
prev parent reply other threads:[~2013-04-25 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 11:47 [PATCH] sched: fix the wrong macro name of CONFIG_DEBUG_PREEMPT Qiang Huang
2013-04-09 14:37 ` Steven Rostedt
2013-04-25 16:35 ` Sebastian Andrzej Siewior [this message]
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=20130425163534.GE5561@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=h.huangqiang@huawei.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable-rt@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).