[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4hvv4nhE-9aO1p2+MsCDBAx-8kqwSUQ7FA15LZJAHz=8Q@mail.gmail.com>
Date: Wed, 7 Sep 2016 08:47:13 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Anshuman Khandual <khandual@...ux.vnet.ibm.com>
Cc: "linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
Linux MM <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 5/5] mm: cleanup pfn_t usage in track_pfn_insert()
On Tue, Sep 6, 2016 at 10:12 PM, Anshuman Khandual
<khandual@...ux.vnet.ibm.com> wrote:
> On 09/06/2016 10:19 PM, Dan Williams wrote:
>> Now that track_pfn_insert() is no longer used in the DAX path, it no
>> longer needs to comprehend pfn_t values.
>>
>> Signed-off-by: Dan Williams <dan.j.williams@...el.com>
>> ---
>> arch/x86/mm/pat.c | 4 ++--
>> include/asm-generic/pgtable.h | 4 ++--
>> mm/memory.c | 2 +-
>> 3 files changed, 5 insertions(+), 5 deletions(-)
>
> A small nit. Should not the arch/x86/mm/pat.c changes be separated out
> into a different patch ? Kind of faced little bit problem separating out
> generic core mm changes to that of arch specific mm changes when going
> through the commits in retrospect.
I'm going to drop this change. Leaving it as is does no harm, and
users of pfn_t are likely to grow over time.
Powered by blists - more mailing lists