[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f00f9c93-c115-d222-dc8c-11493ccd2567@redhat.com>
Date: Wed, 29 Jun 2022 09:33:28 +0200
From: David Hildenbrand <david@...hat.com>
To: Alex Sierra <alex.sierra@....com>, jgg@...dia.com
Cc: Felix.Kuehling@....com, linux-mm@...ck.org, rcampbell@...dia.com,
linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org,
amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
hch@....de, jglisse@...hat.com, apopple@...dia.com,
willy@...radead.org, akpm@...ux-foundation.org
Subject: Re: [PATCH v7 01/14] mm: rename is_pinnable_pages to
is_pinnable_longterm_pages
On 29.06.22 05:54, Alex Sierra wrote:
> is_pinnable_page() and folio_is_pinnable() were renamed to
> is_longterm_pinnable_page() and folio_is_longterm_pinnable()
> respectively. These functions are used in the FOLL_LONGTERM flag
> context.
Subject talks about "*_pages"
Can you elaborate why the move from mm.h to memremap.h is justified?
I'd have called it "is_longterm_pinnable_page", but I am not a native
speaker, so no strong opinion :)
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists