From: kernel test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: [djbw-nvdimm:libnvdimm-pending 16/22] drivers/dax/mapping.c:646: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Date: Wed, 14 Sep 2022 18:09:18 +0800 [thread overview]
Message-ID: <202209141710.pI0d0v9N-lkp@intel.com> (raw)
Hi Dan,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git libnvdimm-pending
head: e27a0356de15f16934325784c6b1d89cf0f13458
commit: 155ac6b670cf6385f6dd14910560d569560af889 [16/22] devdax: Move address_space helpers to the DAX core
config: x86_64-randconfig-a015 (https://download.01.org/0day-ci/archive/20220914/202209141710.pI0d0v9N-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git/commit/?id=155ac6b670cf6385f6dd14910560d569560af889
git remote add djbw-nvdimm https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git
git fetch --no-tags djbw-nvdimm libnvdimm-pending
git checkout 155ac6b670cf6385f6dd14910560d569560af889
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/dax/mapping.c:646: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Return NULL if the entry is zapped and all pages in the entry are
vim +646 drivers/dax/mapping.c
644
645 /**
> 646 * Return NULL if the entry is zapped and all pages in the entry are
647 * idle, otherwise return the non-idle page in the entry
648 */
649 static struct page *dax_zap_pages(struct xa_state *xas, void *entry)
650 {
651 struct page *ret = NULL;
652 unsigned long pfn;
653 bool zap;
654
655 if (!dax_entry_size(entry))
656 return NULL;
657
658 zap = !dax_is_zapped(entry);
659
660 for_each_mapped_pfn(entry, pfn) {
661 struct page *page = pfn_to_page(pfn);
662
663 if (zap)
664 page_ref_dec(page);
665
666 if (!ret && !dax_page_idle(page))
667 ret = page;
668 }
669
670 if (zap)
671 dax_zap_entry(xas, entry);
672
673 return ret;
674 }
675
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-14 10:10 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=202209141710.pI0d0v9N-lkp@intel.com \
--to=lkp@intel.com \
--cc=dan.j.williams@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®