From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, peterx@redhat.com, lkp@intel.com,
akpm@linux-foundation.org
Subject: [folded-merged] mm-shmem-handle-uffd-wp-during-fork-fix.patch removed from -mm tree
Date: Thu, 12 May 2022 19:55:50 -0700 [thread overview]
Message-ID: <20220513025551.1C49AC385B8@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/shmem: vma_needs_copy can be static
has been removed from the -mm tree. Its filename was
mm-shmem-handle-uffd-wp-during-fork-fix.patch
This patch was dropped because it was folded into mm-hugetlb-handle-uffd-wp-during-fork.patch
------------------------------------------------------
From: kernel test robot <lkp@intel.com>
Subject: mm/shmem: vma_needs_copy can be static
mm/memory.c:1238:1: warning: symbol 'vma_needs_copy' was not declared. Should it be static?
Link: https://lkml.kernel.org/r/Ylb0CGeFJlc4EzLk@7ec4ff11d4ae
Fixes: 729c63ce2bbd ("mm/shmem: handle uffd-wp during fork()")
Signed-off-by: kernel test robot <lkp@intel.com>
Reported-by: kernel test robot <lkp@intel.com>
Acked-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/memory.c~mm-shmem-handle-uffd-wp-during-fork-fix
+++ a/mm/memory.c
@@ -1234,7 +1234,7 @@ copy_p4d_range(struct vm_area_struct *ds
* false when we can speed up fork() by allowing lazy page faults later until
* when the child accesses the memory range.
*/
-bool
+static bool
vma_needs_copy(struct vm_area_struct *dst_vma, struct vm_area_struct *src_vma)
{
/*
_
Patches currently in -mm which might be from lkp@intel.com are
mm-hugetlb-handle-uffd-wp-during-fork.patch
reply other threads:[~2022-05-13 2:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220513025551.1C49AC385B8@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mm-commits@vger.kernel.org \
--cc=peterx@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.