From: "Liu, Yujie" <yujie.liu@intel.com>
To: "21cnbao@gmail.com" <21cnbao@gmail.com>, lkp <lkp@intel.com>
Cc: "v-songbaohua@oppo.com" <v-songbaohua@oppo.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 6728/7105] mm/rmap.c:1413: warning: Function parameter or struct member 'flags' not described in 'folio_add_new_anon_rmap'
Date: Thu, 20 Jun 2024 06:57:43 +0000 [thread overview]
Message-ID: <49425b13ccc4d20bb2d08a3b94a710a12f281b96.camel@intel.com> (raw)
In-Reply-To: <20240619210641.62542-1-21cnbao@gmail.com>
On Thu, 2024-06-20 at 09:06 +1200, Barry Song wrote:
> >
> > tree:
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > master
> > head: 2102cb0d050d34d50b9642a3a50861787527e922
> > commit: 41bb9aa5f614423659ced668d0f1ff0c1da6552e [6728/7105] mm:
> > extend rmap flags arguments for folio_add_new_anon_rmap
> > config: arm-pxa910_defconfig
> > (https://download.01.org/0day-ci/archive/20240620/202406200059.tVU9
> > semU-lkp@intel.com/config)
> > compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
> > reproduce (this is a W=1 build):
> > (https://download.01.org/0day-ci/archive/20240620/202406200059.tVU9
> > semU-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a
> > new version of
> > the same patch/commit), kindly add following tags
> > > Reported-by: kernel test robot <lkp@intel.com>
> > > Closes:
> > > https://lore.kernel.org/oe-kbuild-all/202406200059.tVU9semU-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > > > mm/rmap.c:1413: warning: Function parameter or struct member
> > > > 'flags' not described in 'folio_add_new_anon_rmap'
> >
>
> Hi, Thanks very much for the report!
>
> Would you test if the below patch fix the WARNING?
Thanks for sending the patch. It fixes the doc warning for me.
Tested-by: Yujie Liu <yujie.liu@intel.com>
> From: Barry Song <v-songbaohua@oppo.com>
> Date: Thu, 20 Jun 2024 08:57:55 +1200
> Subject: [PATCH] mm: fix the missing doc for flags of
> folio_add_new_anon_rmap()
>
> Fix mm/rmap.c:1413: warning: Function parameter or struct member
> 'flags' not described in 'folio_add_new_anon_rmap'.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes:
> https://lore.kernel.org/oe-kbuild-all/202406200059.tVU9semU-lkp@intel.com/
> Signed-off-by: Barry Song <v-songbaohua@oppo.com>
> ---
> mm/rmap.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/rmap.c b/mm/rmap.c
> index 9b7310120ccb..df1a43295c85 100644
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -1390,6 +1390,7 @@ void folio_add_anon_rmap_pmd(struct folio
> *folio, struct page *page,
> * @folio: The folio to add the mapping to.
> * @vma: the vm area in which the mapping is added
> * @address: the user virtual address mapped
> + * @flags: The rmap flags
> *
> * Like folio_add_anon_rmap_*() but must only be called on *new*
> folios.
> * This means the inc-and-test can be bypassed.
prev parent reply other threads:[~2024-06-20 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 16:41 kernel test robot
2024-06-19 21:06 ` Barry Song
2024-06-20 6:57 ` Liu, Yujie [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=49425b13ccc4d20bb2d08a3b94a710a12f281b96.camel@intel.com \
--to=yujie.liu@intel.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=v-songbaohua@oppo.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