From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Ingo Molnar <mingo@elte.hu>, Mike Galbraith <efault@gmx.de>,
Linux Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: Make sure task has correct sched_class after policy change
Date: Mon, 12 Oct 2009 17:34:13 +0200 [thread overview]
Message-ID: <1255361653.10420.32.camel@twins> (raw)
In-Reply-To: <4AD27A25.8030802@bigpond.net.au>
On Mon, 2009-10-12 at 10:36 +1000, Peter Williams wrote:
> What ever happened to this patch? It doesn't seem to have made it into
> the main line yet.
I,.. uhm,.. guess I'm turning senile and utterly forgot about it.
Queued it, thanks for reminding me!
next prev parent reply other threads:[~2009-10-12 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 2:21 [PATCH] sched: Make sure task has correct sched_class after policy change Peter Williams
2009-09-23 6:32 ` Peter Zijlstra
2009-09-23 12:40 ` Peter Williams
2009-10-12 0:36 ` Peter Williams
2009-10-12 15:34 ` Peter Zijlstra [this message]
2009-10-14 13:13 ` [tip:sched/urgent] " tip-bot for Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2009-09-23 2:03 [PATCH] " Peter Williams
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=1255361653.10420.32.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pwil3058@bigpond.net.au \
/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