From: kbuild test robot <lkp@intel.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: kbuild-all@01.org, linux-btrfs@vger.kernel.org,
Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Subject: Re: [PATCH v12.2 03/15] btrfs: dedupe: Introduce function to initialize dedupe info
Date: Mon, 25 Jul 2016 16:17:53 +0800 [thread overview]
Message-ID: <201607251615.6RqTIVWC%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160719085050.30564-4-quwenruo@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
Hi,
[auto build test ERROR on next-20160724]
[cannot apply to btrfs/next linus/master stable/master v4.7-rc7 v4.7-rc6 v4.7-rc5 v4.7]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Qu-Wenruo/Btrfs-In-band-De-duplication/20160725-140320
config: i386-randconfig-s0-07250950 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
fs/built-in.o: In function `btrfs_dedupe_enable':
>> (.text+0xd3c77b): undefined reference to `__udivdi3'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 26696 bytes --]
next prev parent reply other threads:[~2016-07-25 8:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 8:50 [PATCH v12.2 00/15] Btrfs In-band De-duplication Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 01/15] btrfs: expand btrfs_set_extent_delalloc() and its friends to support in-band dedupe and subpage size patchset Qu Wenruo
2016-08-09 1:19 ` Qu Wenruo
2016-09-07 14:53 ` David Sterba
2016-07-19 8:50 ` [PATCH v12.2 02/15] btrfs: dedupe: Introduce dedupe framework and its header Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 03/15] btrfs: dedupe: Introduce function to initialize dedupe info Qu Wenruo
2016-07-25 8:17 ` kbuild test robot [this message]
2016-07-19 8:50 ` [PATCH v12.2 04/15] btrfs: dedupe: Introduce function to add hash into in-memory tree Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 05/15] btrfs: dedupe: Introduce function to remove hash from " Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 06/15] btrfs: delayed-ref: Add support for increasing data ref under spinlock Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 07/15] btrfs: dedupe: Introduce function to search for an existing hash Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 08/15] btrfs: dedupe: Implement btrfs_dedupe_calc_hash interface Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 09/15] btrfs: ordered-extent: Add support for dedupe Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 10/15] btrfs: dedupe: Inband in-memory only de-duplication implement Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 11/15] btrfs: dedupe: Add ioctl for inband dedupelication Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 12/15] btrfs: relocation: Enhance error handling to avoid BUG_ON Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 13/15] btrfs: improve inode's outstanding_extents computation Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 14/15] btrfs: dedupe: fix false ENOSPC Qu Wenruo
2016-07-19 8:50 ` [PATCH v12.2 15/15] btrfs: dedupe: Introduce new reconfigure ioctl Qu Wenruo
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=201607251615.6RqTIVWC%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=wangxg.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).