public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: kbuild-all@lists.01.org, Chao Yu <yuchao0@huawei.com>,
	Chao Yu <chao@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [chao-linux:feature/dax 6/11] fs/f2fs/data.c:4262:16: error: implicit declaration of function 'dax_writeback_mapping_range'
Date: Thu, 26 Aug 2021 08:13:27 +0800	[thread overview]
Message-ID: <202108260823.45d7ARgR-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git feature/dax
head:   1e51aff10ad27548ead6f2d7c0198bcb969fd631
commit: 7b903d19055bf2665d9b5a895ecf5fc5d89e93ca [6/11] f2fs: support dax address space operation
config: alpha-randconfig-c024-20210825 (attached as .config)
compiler: alpha-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?id=7b903d19055bf2665d9b5a895ecf5fc5d89e93ca
        git remote add chao-linux https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git
        git fetch --no-tags chao-linux feature/dax
        git checkout 7b903d19055bf2665d9b5a895ecf5fc5d89e93ca
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=alpha 

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/f2fs/data.c: In function 'f2fs_dax_writepages':
>> fs/f2fs/data.c:4262:16: error: implicit declaration of function 'dax_writeback_mapping_range' [-Werror=implicit-function-declaration]
    4262 |         return dax_writeback_mapping_range(mapping, sbi->s_daxdev, wbc);
         |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~
   fs/f2fs/data.c:4262:56: error: 'struct f2fs_sb_info' has no member named 's_daxdev'
    4262 |         return dax_writeback_mapping_range(mapping, sbi->s_daxdev, wbc);
         |                                                        ^~
   fs/f2fs/data.c:4263:1: error: control reaches end of non-void function [-Werror=return-type]
    4263 | }
         | ^
   cc1: some warnings being treated as errors


vim +/dax_writeback_mapping_range +4262 fs/f2fs/data.c

  4253	
  4254	static int f2fs_dax_writepages(struct address_space *mapping,
  4255						struct writeback_control *wbc)
  4256	{
  4257		struct f2fs_sb_info *sbi = F2FS_I_SB(mapping->host);
  4258	
  4259		if (unlikely(f2fs_cp_error(sbi)))
  4260			return -EIO;
  4261	
> 4262		return dax_writeback_mapping_range(mapping, sbi->s_daxdev, wbc);
  4263	}
  4264	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33210 bytes --]

                 reply	other threads:[~2021-08-26  0:13 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=202108260823.45d7ARgR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chao@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.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