[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180921103141.GB15555@techadventures.net>
Date: Fri, 21 Sep 2018 12:31:41 +0200
From: Oscar Salvador <osalvador@...hadventures.net>
To: Pasha Tatashin <Pavel.Tatashin@...rosoft.com>
Cc: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"mhocko@...e.com" <mhocko@...e.com>,
"dan.j.williams@...el.com" <dan.j.williams@...el.com>,
"david@...hat.com" <david@...hat.com>,
"Jonathan.Cameron@...wei.com" <Jonathan.Cameron@...wei.com>,
"yasu.isimatu@...il.com" <yasu.isimatu@...il.com>,
"malat@...ian.org" <malat@...ian.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Oscar Salvador <osalvador@...e.de>
Subject: Re: [PATCH 2/5] mm/memory_hotplug: Avoid
node_set/clear_state(N_HIGH_MEMORY) when !CONFIG_HIGHMEM
On Thu, Sep 20, 2018 at 08:59:18PM +0000, Pasha Tatashin wrote:
> This is a rare case where I think comments are unnecessary as the code
> is self explanatory. So, I would remove the comments before:
Fair enough.
I just wanted to make clear why it was not needed.
I will remove it in the next version.
Thanks
--
Oscar Salvador
SUSE L3
Powered by blists - more mailing lists