From: Peter Xu <peterx@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH linux-next] mm/shmem: vma_needs_copy can be static
Date: Wed, 13 Apr 2022 12:51:54 -0400 [thread overview]
Message-ID: <Ylb/qmmwZlVnwYPe@xz-m1.local> (raw)
In-Reply-To: <Ylb0CGeFJlc4EzLk@7ec4ff11d4ae>
On Thu, Apr 14, 2022 at 12:02:16AM +0800, kernel test robot wrote:
> mm/memory.c:1238:1: warning: symbol 'vma_needs_copy' was not declared. Should it be static?
>
> Fixes: 729c63ce2bbd ("mm/shmem: handle uffd-wp during fork()")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: kernel test robot <lkp@intel.com>
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
prev parent reply other threads:[~2022-04-13 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 16:04 [linux-next:master 3834/3955] mm/memory.c:1238:1: sparse: sparse: symbol 'vma_needs_copy' was not declared. Should it be static? kernel test robot
2022-04-13 16:02 ` [RFC PATCH linux-next] mm/shmem: vma_needs_copy can be static kernel test robot
2022-04-13 16:51 ` Peter Xu [this message]
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=Ylb/qmmwZlVnwYPe@xz-m1.local \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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