[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111104151631.GW4417@google.com>
Date: Fri, 4 Nov 2011 08:16:31 -0700
From: Tejun Heo <tj@...nel.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: paul@...lmenage.org, rjw@...k.pl, lizf@...fujitsu.com,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
containers@...ts.linux-foundation.org, fweisbec@...il.com,
matthltc@...ibm.com, akpm@...ux-foundation.org, oleg@...hat.com
Subject: Re: [PATCH 02/10] threadgroup: rename
signal->threadgroup_fork_lock to ->group_rwsem
On Fri, Nov 04, 2011 at 05:40:32PM +0900, KAMEZAWA Hiroyuki wrote:
> On Tue, 1 Nov 2011 16:46:25 -0700
> Tejun Heo <tj@...nel.org> wrote:
>
> > Make the following renames to prepare for extension of threadgroup
> > locking.
> >
> > * s/signal->threadgroup_fork_lock/signal->group_rwsem/
> > * s/threadgroup_fork_read_lock()/threadgroup_change_begin()/
> > * s/threadgroup_fork_read_unlock()/threadgroup_change_done()/
>
> I personally like begin <-> end to see relationship.
Hmmm... yeah, I like that better too. Renaming.
Thanks.
--
tejun
--
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/
Powered by blists - more mailing lists