From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@kernel.org, pjt@google.com, venki@google.com,
efault@gmx.de, glommer@parallels.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 2/4] sched: Push put_prev_task() into pick_next_task()
Date: Thu, 14 Jun 2012 16:58:00 +0200 [thread overview]
Message-ID: <1339685880.2559.38.camel@twins> (raw)
In-Reply-To: <1339684321.13377.215.camel@gandalf.stny.rr.com>
On Thu, 2012-06-14 at 10:32 -0400, Steven Rostedt wrote:
>
> You remove the call to put_prev_task() which looks to be the only user
> of this static function. But I don't see the deletion of this
> function.
>
>
Right you are.. must've overlooked my compiler complaining about this.
next prev parent reply other threads:[~2012-06-14 14:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 13:29 [RFC][PATCH 0/4] sched: Optimize cgroup muck Peter Zijlstra
2012-06-14 13:29 ` [RFC][PATCH 1/4] sched/fair: track cgroup depth Peter Zijlstra
2012-06-14 13:29 ` [RFC][PATCH 2/4] sched: Push put_prev_task() into pick_next_task() Peter Zijlstra
2012-06-14 14:32 ` Steven Rostedt
2012-06-14 14:58 ` Peter Zijlstra [this message]
2012-06-15 9:49 ` Glauber Costa
2012-06-15 10:03 ` Peter Zijlstra
2012-06-15 10:01 ` Glauber Costa
2012-06-21 7:35 ` Michael Wang
2012-06-21 8:41 ` Peter Zijlstra
2012-06-21 9:23 ` Michael Wang
2012-06-14 13:29 ` [RFC][PATCH 3/4] sched/fair: clean up __clear_buddies_* Peter Zijlstra
2012-06-14 13:29 ` [RFC][PATCH 4/4] sched/fair: Optimize cgroup pick_next_task_fair Peter Zijlstra
2012-06-14 21:19 ` Peter Zijlstra
2012-06-15 14:03 ` Peter Zijlstra
2012-06-19 8:45 ` Paul Turner
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=1339685880.2559.38.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=glommer@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=venki@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.