From: kbuild test robot <lkp@intel.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: kbuild-all@01.org, linux-btrfs@vger.kernel.org,
Nikolay Borisov <nborisov@suse.com>
Subject: Re: [PATCH 1/2] btrfs: remove unused sectorsize member
Date: Tue, 27 Jun 2017 19:22:48 +0800 [thread overview]
Message-ID: <201706271951.Ut2vb3Jv%fengguang.wu@intel.com> (raw)
In-Reply-To: <1498488155-9941-1-git-send-email-nborisov@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2325 bytes --]
Hi Nikolay,
[auto build test ERROR on v4.12-rc6]
[also build test ERROR on next-20170627]
[cannot apply to btrfs/next]
[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/Nikolay-Borisov/btrfs-remove-unused-sectorsize-member/20170627-183835
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All errors (new ones prefixed by >>):
fs/btrfs/tests/btrfs-tests.c: In function 'btrfs_alloc_dummy_block_group':
>> fs/btrfs/tests/btrfs-tests.c:214:7: error: 'struct btrfs_block_group_cache' has no member named 'sectorsize'
cache->sectorsize = fs_info->sectorsize;
^
--
fs/btrfs/tests/free-space-tree-tests.c: In function '__check_free_space_extents':
>> fs/btrfs/tests/free-space-tree-tests.c:84:20: error: 'struct btrfs_block_group_cache' has no member named 'sectorsize'
offset += cache->sectorsize;
^
vim +214 fs/btrfs/tests/btrfs-tests.c
7c55ee0c Omar Sandoval 2015-09-29 208 return NULL;
7c55ee0c Omar Sandoval 2015-09-29 209 }
7c55ee0c Omar Sandoval 2015-09-29 210
7c55ee0c Omar Sandoval 2015-09-29 211 cache->key.objectid = 0;
7c55ee0c Omar Sandoval 2015-09-29 212 cache->key.offset = length;
7c55ee0c Omar Sandoval 2015-09-29 213 cache->key.type = BTRFS_BLOCK_GROUP_ITEM_KEY;
da17066c Jeff Mahoney 2016-06-15 @214 cache->sectorsize = fs_info->sectorsize;
da17066c Jeff Mahoney 2016-06-15 215 cache->full_stripe_len = fs_info->sectorsize;
da17066c Jeff Mahoney 2016-06-15 216 cache->fs_info = fs_info;
7c55ee0c Omar Sandoval 2015-09-29 217
:::::: The code at line 214 was first introduced by commit
:::::: da17066c40472c2d6a1aab7bb0090c3d285531c9 btrfs: pull node/sector/stripe sizes out of root and into fs_info
:::::: TO: Jeff Mahoney <jeffm@suse.com>
:::::: CC: David Sterba <dsterba@suse.com>
---
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: 50281 bytes --]
next prev parent reply other threads:[~2017-06-27 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 14:42 [PATCH 1/2] btrfs: remove unused sectorsize member Nikolay Borisov
2017-06-26 14:42 ` [PATCH 2/2] btrfs: Optimise layout of btrfs_block_group_cache Nikolay Borisov
2017-06-26 15:30 ` Nikolay Borisov
2017-06-27 17:11 ` David Sterba
2017-06-27 11:22 ` kbuild test robot [this message]
2017-06-27 13:25 ` [PATCH v2] btrfs: remove unused sectorsize member Nikolay Borisov
2017-06-27 17:13 ` David Sterba
2017-06-28 8:05 ` [PATCH v3] " Nikolay Borisov
2017-06-30 8:07 ` David Sterba
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=201706271951.Ut2vb3Jv%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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).