From: "Peter W. Morreale" <pmorreale@novell.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, comandante@zaralinux.com,
bb@ricochet.net, Rik van Riel <riel@nl.linux.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Update of Documentation/ (VM sysctls)
Date: Fri, 02 Jan 2009 08:25:01 -0700 [thread overview]
Message-ID: <1230909901.3470.242.camel@hermosa.site> (raw)
In-Reply-To: <495D9222.1060306@oracle.com>
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?
Thx,
-PWM
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-01-02 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081231212615.12868.97088.stgit@hermosa.site>
2009-01-02 4:03 ` Randy Dunlap
2009-01-02 15:25 ` Peter W. Morreale [this message]
2009-01-02 16:29 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1230909901.3470.242.camel@hermosa.site \
--to=pmorreale@novell.com \
--cc=akpm@linux-foundation.org \
--cc=bb@ricochet.net \
--cc=comandante@zaralinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=randy.dunlap@oracle.com \
--cc=riel@nl.linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox