[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231016155512.6e48836f3baef1c899bcae91@linux-foundation.org>
Date: Mon, 16 Oct 2023 15:55:12 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mike Kravetz <mike.kravetz@...cle.com>
Cc: Naoya Horiguchi <naoya.horiguchi@...ux.dev>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Muchun Song <songmuchun@...edance.com>,
Joao Martins <joao.m.martins@...cle.com>,
Oscar Salvador <osalvador@...e.de>,
David Hildenbrand <david@...hat.com>,
Miaohe Lin <linmiaohe@...wei.com>,
David Rientjes <rientjes@...gle.com>,
Anshuman Khandual <anshuman.khandual@....com>,
Michal Hocko <mhocko@...e.com>,
Matthew Wilcox <willy@...radead.org>,
Xiongchun Duan <duanxiongchun@...edance.com>
Subject: Re: [PATCH v2 01/11] hugetlb: set hugetlb page flag before
optimizing vmemmap
On Fri, 13 Oct 2023 14:43:56 -0700 Mike Kravetz <mike.kravetz@...cle.com> wrote:
> > Could you consider adding some diff like below?
>
> Thanks! That case was indeed overlooked.
>
> Andrew, this patch is currently in mm-stable. How would you like to update?
> - A new version of the patch
> - An patch to the original patch
> - Something else
I guess just a fixup against what's currently in mm-stable, please. It
happens sometimes.
Please let's get the Fixes: accurate. I just had to rebase mm-stable
to drop Huang Ying's pcp auto-tuning series. I'm now seeing
d8f5f7e445f0 hugetlb: set hugetlb page flag before optimizing vmemmap
which I think is what it used to be, so the rebasing shouldn't affect
this patch's hash.
Powered by blists - more mailing lists