From: Suren Baghdasaryan <surenb@google.com>
To: David Hildenbrand <david@redhat.com>
Cc: akpm@linux-foundation.org, sfr@canb.auug.org.au,
error27@gmail.com, willy@infradead.org, Liam.Howlett@oracle.com,
jgg@ziepe.ca, yuzhao@google.com, dhowells@redhat.com,
hughd@google.com, mathieu.desnoyers@efficios.com,
pasha.tatashin@soleen.com, laurent.dufour@fr.ibm.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mm: document FAULT_FLAG_VMA_LOCK flag
Date: Wed, 1 Mar 2023 09:57:37 -0800 [thread overview]
Message-ID: <CAJuCfpFwvgs-_M60qNA6aJHi3qQ0+WB=zcBGbFPbqJ8tu=5m-w@mail.gmail.com> (raw)
In-Reply-To: <a45e3136-bc88-2de2-4127-62e103656242@redhat.com>
On Wed, Mar 1, 2023 at 12:27 AM David Hildenbrand <david@redhat.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@canb.auug.org.au>
> > Link: https://lore.kernel.org/all/20230301113648.7c279865@canb.auug.org.au/
> > Signed-off-by: Suren Baghdasaryan <surenb@google.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
>
next prev parent reply other threads:[~2023-03-01 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 2:27 [PATCH 1/2] mm/mmap: remove unnecessary vp->vma check in vma_prepare Suren Baghdasaryan
2023-03-01 2:27 ` [PATCH 2/2] mm: document FAULT_FLAG_VMA_LOCK flag Suren Baghdasaryan
2023-03-01 8:27 ` David Hildenbrand
2023-03-01 17:57 ` Suren Baghdasaryan [this message]
2023-03-01 8:26 ` [PATCH 1/2] mm/mmap: remove unnecessary vp->vma check in vma_prepare David Hildenbrand
2023-03-01 14:10 ` Liam R. Howlett
2023-03-01 17:54 ` Suren Baghdasaryan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJuCfpFwvgs-_M60qNA6aJHi3qQ0+WB=zcBGbFPbqJ8tu=5m-w@mail.gmail.com' \
--to=surenb@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=error27@gmail.com \
--cc=hughd@google.com \
--cc=jgg@ziepe.ca \
--cc=laurent.dufour@fr.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=pasha.tatashin@soleen.com \
--cc=sfr@canb.auug.org.au \
--cc=willy@infradead.org \
--cc=yuzhao@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox