[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJuCfpFwvgs-_M60qNA6aJHi3qQ0+WB=zcBGbFPbqJ8tu=5m-w@mail.gmail.com>
Date: Wed, 1 Mar 2023 09:57:37 -0800
From: Suren Baghdasaryan <surenb@...gle.com>
To: David Hildenbrand <david@...hat.com>
Cc: akpm@...ux-foundation.org, 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 Wed, Mar 1, 2023 at 12:27 AM David Hildenbrand <david@...hat.com> wrote:
>
> 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.
Yeah, both fixes in this patchset could be squashed into the original
series without information loss. I'll leave that to Andrew to decide
what makes more sense here.
Thanks!
>
> --
> Thanks,
>
> David / dhildenb
>
Powered by blists - more mailing lists