From: kbuild test robot <lkp@intel.com>
To: Steve Kenton <skenton@ou.edu>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
Steve Kenton <skenton@ou.edu>
Subject: Re: [PATCH V4 1/1] fs/udf sanitize types, use consistent naming and add kernel doc comment
Date: Sun, 15 Jan 2017 18:45:16 +0800 [thread overview]
Message-ID: <201701151806.3miW3ihV%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170115041839.32311-1-skenton@ou.edu>
[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]
Hi Steve,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc3 next-20170113]
[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/Steve-Kenton/fs-udf-sanitize-types-use-consistent-naming-and-add-kernel-doc-comment/20170115-133615
config: arm-axm55xx_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm
All errors (new ones prefixed by >>):
fs/built-in.o: In function `udf_bitmap_free_blocks':
>> fs/udf/balloc.c:176: undefined reference to `__aeabi_uldivmod'
fs/built-in.o: In function `udf_bitmap_prealloc_blocks':
fs/udf/balloc.c:253: undefined reference to `__aeabi_uldivmod'
fs/built-in.o: In function `udf_bitmap_new_block':
fs/udf/balloc.c:313: undefined reference to `__aeabi_uldivmod'
vim +176 fs/udf/balloc.c
c436c511 Steve Kenton 2017-01-14 170 block = eloc->logicalBlockNum + offset +
4b11111a Marcin Slusarz 2008-02-08 171 (sizeof(struct spaceBitmapDesc) << 3);
^1da177e Linus Torvalds 2005-04-16 172
4daa1b87 Marcin Slusarz 2008-02-08 173 do {
^1da177e Linus Torvalds 2005-04-16 174 overflow = 0;
^1da177e Linus Torvalds 2005-04-16 175 block_group = block >> (sb->s_blocksize_bits + 3);
^1da177e Linus Torvalds 2005-04-16 @176 bit = block % (sb->s_blocksize << 3);
^1da177e Linus Torvalds 2005-04-16 177
^1da177e Linus Torvalds 2005-04-16 178 /*
^1da177e Linus Torvalds 2005-04-16 179 * Check to see if we are freeing blocks across a group boundary.
:::::: The code at line 176 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
---
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: 19665 bytes --]
next prev parent reply other threads:[~2017-01-15 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 4:18 [PATCH V4 1/1] fs/udf sanitize types, use consistent naming and add kernel doc comment Steve Kenton
2017-01-15 10:45 ` kbuild test robot [this message]
2017-01-15 13:45 ` kbuild test robot
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=201701151806.3miW3ihV%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=skenton@ou.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;
as well as URLs for NNTP newsgroup(s).