[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20111227160224.c59080e6.akpm@linux-foundation.org>
Date: Tue, 27 Dec 2011 16:02:24 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Valdis.Kletnieks@...edu
Cc: Cyrill Gorcunov <gorcunov@...nvz.org>,
linux-kernel@...r.kernel.org,
Pavel Emelyanov <xemul@...allels.com>,
Glauber Costa <glommer@...allels.com>,
Andi Kleen <andi@...stfloor.org>, Tejun Heo <tj@...nel.org>,
Matt Helsley <matthltc@...ibm.com>,
Pekka Enberg <penberg@...nel.org>,
Eric Dumazet <eric.dumazet@...il.com>,
Vasiliy Kulikov <segoon@...nwall.com>,
Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: [patch 1/4] Add routine for generating an ID for kernel pointer
On Tue, 27 Dec 2011 18:54:29 -0500
Valdis.Kletnieks@...edu wrote:
> > +config GENERIC_OBJECT_ID
> > + bool "Enable generic object ID infrastructure"
> > + depends on CHECKPOINT_RESTORE
> > + default n
> > + help
> > + Turn on the functionality that can generate IDs for kernel
>
> "Turn on functionality"
>
> > + objects, which are exported to userspace via /proc filesystem.
>
> Lose the ,
>
> > +
> > + It is useful if you need to examinate kernel objects and test
>
> examine
>
> > + if they are shared between several tasks. These IDs should never
> > + be used for anything but the "sameness" test. Besides, the IDs are
>
> s/Besides, the/The/
>
> > + dynamic and valid only while object is alive, once it get freed or
>
> s/alive, once/alive. Once/
>
> > + kernel is rebooted -- the IDs will be changed.
>
> s/ --/,/
heh, I avoided mentioning these things because I usually rewrite the
user-facing text when merging patches from non-native English speakers.
--
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