linux-kernel - Re: [PATCH] sched: consolidate the name of root_task_group and init_task

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1294390754.2016.392.camel@laptop>
Date:	Fri, 07 Jan 2011 09:59:14 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Yong Zhang <yong.zhang0@...il.com>
Cc:	Mike Galbraith <efault@....de>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] sched: consolidate the name of root_task_group and
 init_task_group

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@...il.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@....de>
> Signed-off-by: Yong Zhang <yong.zhang0@...il.com>
> Cc: Ingo Molnar <mingo@...e.hu>
> Cc: Peter Zijlstra <peterz@...radead.org> 

OK, took this one instead..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/