All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] sched: consolidate the name of root_task_group and init_task_group
Date: Fri, 07 Jan 2011 09:59:14 +0100	[thread overview]
Message-ID: <1294390754.2016.392.camel@laptop> (raw)
In-Reply-To: <20110107071736.GA32635@windriver.com>

On Fri, 2011-01-07 at 15:17 +0800, Yong Zhang wrote:
> Well, I have no bias to either of them. Keeping init_task_group is
> just that we can touch less lines. :)
> 
> If you want root_task_group, here it is:
> ---
> From: Yong Zhang <yong.zhang0@gmail.com>
> Subject: [PATCH] sched: consolidate the name of root_task_group and
> init_task_group
> 
> root_task_group is the leftover of USER_SCHED, now it's always
> same to init_task_group.
> But as Mike suggested, root_task_group is maybe the suitable name
> to keep for a tree.
> So in this patch:
>   init_task_group      --> root_task_group
>   init_task_group_load --> root_task_group_load
>   INIT_TASK_GROUP_LOAD --> ROOT_TASK_GROUP_LOAD
> 
> Suggested-by: Mike Galbraith <efault@gmx.de>
> Signed-off-by: Yong Zhang <yong.zhang0@gmail.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Peter Zijlstra <peterz@infradead.org> 

OK, took this one instead..

  reply	other threads:[~2011-01-07  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07  4:43 [PATCH] sched: remove root_task_group Yong Zhang
2011-01-07  5:42 ` Mike Galbraith
2011-01-07  7:17   ` [PATCH] sched: consolidate the name of root_task_group and init_task_group Yong Zhang
2011-01-07  8:59     ` Peter Zijlstra [this message]
2011-01-07 15:35     ` [tip:sched/urgent] sched: Consolidate " tip-bot for Yong Zhang
2011-01-07  8:57 ` [PATCH] sched: remove root_task_group 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=1294390754.2016.392.camel@laptop \
    --to=peterz@infradead.org \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yong.zhang0@gmail.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.