[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171019042859.GX5109@tassilo.jf.intel.com>
Date: Wed, 18 Oct 2017 21:28:59 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: "Sandoval Castro, Luis Felipe"
<luis.felipe.sandoval.castro@...el.com>
Cc: Michal Hocko <mhocko@...nel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"vbabka@...e.cz" <vbabka@...e.cz>,
"mingo@...nel.org" <mingo@...nel.org>,
"rientjes@...gle.com" <rientjes@...gle.com>,
"n-horiguchi@...jp.nec.com" <n-horiguchi@...jp.nec.com>,
"salls@...ucsb.edu" <salls@...ucsb.edu>,
Cristopher Lameter <cl@...ux.com>
Subject: Re: [PATCH v1] mm/mempolicy.c: Fix get_nodes() off-by-one error.
On Thu, Oct 19, 2017 at 03:48:09AM +0000, Sandoval Castro, Luis Felipe wrote:
> On Tue 18-10-17 10:42:34, Luis Felipe Sandoval Castro wrote:
>
> Sorry for the delayed replay, from your feedback I don't think my
> patch has any chances of being merged... I'm wondering though,
> if a note in the man pages "range non inclusive" or something
> like that would help to avoid confusions? Thanks
Yes fixing the man pages is a good idea.
-Andi
Powered by blists - more mailing lists