[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YZJFVK8g8LhWlICo@xz-m1.local>
Date: Mon, 15 Nov 2021 19:37:00 +0800
From: Peter Xu <peterx@...hat.com>
To: Alistair Popple <apopple@...dia.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
Yang Shi <shy828301@...il.com>,
Hugh Dickins <hughd@...gle.com>,
David Hildenbrand <david@...hat.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Vlastimil Babka <vbabka@...e.cz>,
"Kirill A . Shutemov" <kirill@...temov.name>
Subject: Re: [PATCH RFC 2/2] mm: Rework swap handling of zap_pte_range
On Mon, Nov 15, 2021 at 10:21:18PM +1100, Alistair Popple wrote:
> Hi Peter,
Hi, Alistair,
>
> I was having trouble applying this cleanly to any of my local trees so was
> wondering which sha1 should I be applying this on top of? Thanks.
Thanks for considering trying it out. I thought it was easy to apply onto any
of the recent branches as long as with -mm's rc1 applied, and I just did it to
Linus's 5.16-rc1 in my uffd-wp rebase:
https://github.com/xzpeter/linux/commits/uffd-wp-shmem-hugetlbfs
This commit is here:
https://github.com/xzpeter/linux/commit/c32043436282bb352e6fe10eb5fa693340fe5281
It could be that "git rebase" is normally smarter so I didn't notice it's not
applicable directly.
I'll repost a new version soon, please also consider to fetch directly from the
git tree too before I do so.
Thanks,
--
Peter Xu
Powered by blists - more mailing lists