From: kernel test robot <lkp@intel.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [willy-pagecache:for-next 166/179] fs/hostfs/hostfs_kern.c:507:17: error: 'filemap_dirty_folio' undeclared here (not in a function); did you mean 'filemap_get_folio'?
Date: Tue, 15 Mar 2022 16:57:28 +0800 [thread overview]
Message-ID: <202203151604.dZIG5fhk-lkp@intel.com> (raw)
tree: git://git.infradead.org/users/willy/pagecache for-next
head: af564d7369d44fbbe697a5f631fe3bba5ebecd59
commit: 821405cf3ebbd9a17baf9afce08b0562fba04056 [166/179] fs: Convert trivial uses of __set_page_dirty_nobuffers to filemap_dirty_folio
config: um-x86_64_defconfig (https://download.01.org/0day-ci/archive/20220315/202203151604.dZIG5fhk-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce (this is a W=1 build):
git remote add willy-pagecache git://git.infradead.org/users/willy/pagecache
git fetch --no-tags willy-pagecache for-next
git checkout 821405cf3ebbd9a17baf9afce08b0562fba04056
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=um SUBARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> fs/hostfs/hostfs_kern.c:507:17: error: 'filemap_dirty_folio' undeclared here (not in a function); did you mean 'filemap_get_folio'?
507 | .dirty_folio = filemap_dirty_folio,
| ^~~~~~~~~~~~~~~~~~~
| filemap_get_folio
vim +507 fs/hostfs/hostfs_kern.c
503
504 static const struct address_space_operations hostfs_aops = {
505 .writepage = hostfs_writepage,
506 .readpage = hostfs_readpage,
> 507 .dirty_folio = filemap_dirty_folio,
508 .write_begin = hostfs_write_begin,
509 .write_end = hostfs_write_end,
510 };
511
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-15 8:58 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=202203151604.dZIG5fhk-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.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