[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080219084420.f3104e3f.randy.dunlap@oracle.com>
Date: Tue, 19 Feb 2008 08:44:20 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Pavel Emelyanov <xemul@...nvz.org>
Cc: Nick Andrew <nick@...k-andrew.net>, trivial@...nel.org,
linux-kernel@...r.kernel.org, Serge Hallyn <serue@...ibm.com>
Subject: Re: Improve init/Kconfig help descriptions [PATCH 3/9]
On Tue, 19 Feb 2008 18:16:53 +0300 Pavel Emelyanov wrote:
> Nick Andrew wrote:
> > On Tue, Feb 19, 2008 at 05:42:07PM +0300, Pavel Emelyanov wrote:
> >> Nick Andrew wrote:
> >>> On Wed, Feb 20, 2008 at 01:06:09AM +1100, Nick Andrew wrote:
> >>>> Here is a series of 9 patches to init/Kconfig intended to improve the
> >>>> usefulness and consistency of the help descriptions. The patches are
> >>>> against linux-2.6.24.2.
> >>>> [...]
> >>>> Patch 3
> >>>> USER_NS
> >>>> PID_NS
> >> What about UTS_NS, IPC_NS and NET_NS?
> >> Their descriptions can be improved in the same way :)
> >
> > So far I have edited only init/Kconfig, that's what these 9
> > patches are for. Next I'll do block/Kconfig. Eventually I expect
> > to get to net/Kconfig which is where NET_NS is configured,
> > but I don't know where UTS_NS and IPC_NS come from in 2.6.24.2.
> >
> > I expect I'll have to start patching against a git tree soon,
> > to be sure to see the latest code. I assume this should be
> > Linus' tree?
>
> Both UTS_NS and IPC_NS are in init/Kconfg. At least they are
> in 2.6.25-rc2 :)
Yes, these patches should be made against the latest development
tree, not the stable tree.
---
~Randy
--
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