[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <495E40EE.8080904@oracle.com>
Date: Fri, 02 Jan 2009 08:29:34 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: "Peter W. Morreale" <pmorreale@...ell.com>
CC: linux-kernel@...r.kernel.org, comandante@...alinux.com,
bb@...ochet.net, Rik van Riel <riel@...linux.org>,
linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Update of Documentation/ (VM sysctls)
Peter W. Morreale wrote:
> On Thu, 2009-01-01 at 20:03 -0800, Randy Dunlap wrote:
>> Peter W Morreale wrote:
>
>>> It assumes that patch: http://lkml.org/lkml/2008/12/31/219 has been applied.
>>> This is probably wrong since that patch is still being reviewed and not
>>> officially accepted as of this patch. Not sure how to handle this at
>>> all.
>> Yes, this patch should be done first/regardless of your other (pending) patch.
>>
>
> Wait a sec...
>
> There is a patch interdependency here.
>
> This patch includes the text for the two proposed sysctls. If they are
> rejected, then this help text will refer to two non-existent sysctls.
> Minor issue compared to:
>
> The pdflush sysctl patch was respun to include adding text (against the
> current vm.txt) for the new sysctls. So that patch will fail to apply
> should this patch be added first.
>
> See what I mean? So what do I do?
Sorry about the confusion. What I meant was that this patch's concept
(moving VM sysctls to Doc/sysctl/vm.txt) should be done first (without
the new pdflush pieces), then the new pdflush pieces should be done on
top of that first patch. Is that clearer?
--
~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