[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a45e3136-bc88-2de2-4127-62e103656242@redhat.com>
Date: Wed, 1 Mar 2023 09:27:27 +0100
From: David Hildenbrand <david@...hat.com>
To: Suren Baghdasaryan <surenb@...gle.com>, akpm@...ux-foundation.org
Cc: sfr@...b.auug.org.au, error27@...il.com, willy@...radead.org,
Liam.Howlett@...cle.com, jgg@...pe.ca, yuzhao@...gle.com,
dhowells@...hat.com, hughd@...gle.com,
mathieu.desnoyers@...icios.com, pasha.tatashin@...een.com,
laurent.dufour@...ibm.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] mm: document FAULT_FLAG_VMA_LOCK flag
On 01.03.23 03:27, Suren Baghdasaryan wrote:
> FAULT_FLAG_VMA_LOCK flag was introduced without proper description. Fix
> this by documenting it.
>
> Fixes: 863be34fc093 ("mm: add FAULT_FLAG_VMA_LOCK flag")
> Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
> Link: https://lore.kernel.org/all/20230301113648.7c279865@canb.auug.org.au/
> Signed-off-by: Suren Baghdasaryan <surenb@...gle.com>
> ---
> Fix cleanly apply over mm-unstable, SHA in "Fixes" is from that tree.
Okay, that should be squashed then. LGTM.
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists