From: Mel Gorman <mel@csn.ul.ie>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] Add a sysctl for numa_balancing v2
Date: Tue, 7 Jan 2014 23:01:47 +0000 [thread overview]
Message-ID: <20140107230147.GD5990@csn.ul.ie> (raw)
In-Reply-To: <20140107221316.GF20765@two.firstfloor.org>
On Tue, Jan 07, 2014 at 11:13:16PM +0100, Andi Kleen wrote:
> On Tue, Jan 07, 2014 at 01:58:17PM -0800, Andrew Morton wrote:
> > On Mon, 6 Jan 2014 16:08:46 -0800 Andi Kleen <andi@firstfloor.org> wrote:
> >
> > > From: Andi Kleen <ak@linux.intel.com>
> > >
> > > [It turns out the documentation patch was already merged
> > > earlier. So just resending without documentation.]
> >
> > Confused. How could we have merged the documentation for this feature
> > but not the feature itself?
>
> Originally all numa balancing sysctl were undocumented. I had
> a TBD for this in my original patch. Mel then documented them,
> but also included the documentation for the new sysctl in that patch.
> Mel's documentation patch was then merged
> (as part of his regular merges I suppose), but the global sysctl
> patch wasn't.
>
Yeah, it was an oversight on my part. I can't remember if I accidentally
dropped Andi's patch or thought it had been merged already. Sorry.
--
Mel Gorman
SUSE Labs
--
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>
prev parent reply other threads:[~2014-01-07 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 0:08 Andi Kleen
2014-01-07 21:58 ` Andrew Morton
2014-01-07 22:13 ` Andi Kleen
2014-01-07 23:01 ` Mel Gorman [this message]
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=20140107230147.GD5990@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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