From: kbuild test robot <fengguang.wu@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: kbuild-all@01.org, linux-ext4@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>
Subject: [ext4:dev 21/26] file.c:undefined reference to `dax_iomap_fault'
Date: Tue, 22 Nov 2016 04:17:11 +0800 [thread overview]
Message-ID: <201611220402.CuudYzqp%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
head: 19b29dca7eef735531a2448e692bb1658c351887
commit: 8b72e1435cd73926cba767fba3e957807a97069c [21/26] ext4: convert DAX faults to iomap infrastructure
config: i386-randconfig-sb0-11212318 (attached as .config)
compiler: gcc-5 (Debian 5.4.1-2) 5.4.1 20160904
reproduce:
git checkout 8b72e1435cd73926cba767fba3e957807a97069c
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
fs/built-in.o: In function `ext4_dax_fault':
>> file.c:(.text+0x529f3): undefined reference to `dax_iomap_fault'
fs/built-in.o: In function `ext4_file_read_iter':
file.c:(.text+0x52bab): undefined reference to `dax_iomap_rw'
fs/built-in.o: In function `ext4_file_write_iter':
file.c:(.text+0x52dff): undefined reference to `dax_iomap_rw'
fs/built-in.o: In function `ext4_block_zero_page_range':
inode.c:(.text+0x57c8e): undefined reference to `iomap_zero_range'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24511 bytes --]
next reply other threads:[~2016-11-21 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 20:17 kbuild test robot [this message]
2016-11-22 12:08 ` [ext4:dev 21/26] file.c:undefined reference to `dax_iomap_fault' Jan Kara
2016-11-22 21:33 ` Dave Chinner
2016-11-23 8:14 ` Jan Kara
2016-11-23 4:27 ` Theodore Ts'o
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=201611220402.CuudYzqp%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=kbuild-all@01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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