From: Peter Zijlstra <peterz@infradead.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Dario Faggioli <raistlin@linux.it>,
Juri Lelli <juri.lelli@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@linux.intel.com
Subject: Re: [sched] d50dde5a1: LTP sched_setparam* TFAILs
Date: Wed, 15 Jan 2014 14:32:06 +0100 [thread overview]
Message-ID: <20140115133206.GG31570@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140115132609.GA28334@localhost>
On Wed, Jan 15, 2014 at 09:26:09PM +0800, Fengguang Wu wrote:
> It's sched_setparam02 that TFAIL, not sched_setscheduler02. :)
D'0h!
next prev parent reply other threads:[~2014-01-15 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 12:47 [sched] d50dde5a1: LTP sched_setparam* TFAILs Fengguang Wu
2014-01-15 12:49 ` Peter Zijlstra
2014-01-15 13:09 ` Peter Zijlstra
2014-01-15 13:26 ` Fengguang Wu
2014-01-15 13:32 ` Peter Zijlstra [this message]
2014-01-15 15:33 ` [PATCH] sched: Fixup scheduler syscall LTP fails Peter Zijlstra
2014-01-16 13:40 ` [tip:sched/core] sched: Fix up " tip-bot for Peter Zijlstra
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=20140115133206.GG31570@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@linux.intel.com \
--cc=raistlin@linux.it \
/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