From: kbuild test robot <lkp@intel.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org, martin.petersen@oracle.com,
Dmitry Monakhov <dmonakhov@openvz.org>
Subject: Re: [PATCH 6/8] bio-integrity: add bio_integrity_setup helper
Date: Sat, 1 Apr 2017 06:15:21 +0800 [thread overview]
Message-ID: <201704010609.A37RyJqg%fengguang.wu@intel.com> (raw)
In-Reply-To: <1490881776-28735-7-git-send-email-dmonakhov@openvz.org>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
Hi Dmitry,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc4]
[cannot apply to block/for-next next-20170331]
[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/Dmitry-Monakhov/block-T10-DIF-Fixes-and-cleanups/20170401-043532
config: sparc64-defconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
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=sparc64
All errors (new ones prefixed by >>):
In file included from include/linux/blkdev.h:20:0,
from include/linux/backing-dev.h:14,
from include/linux/nfs_fs_sb.h:5,
from include/linux/nfs_fs.h:37,
from arch/sparc/kernel/sys_sparc32.c:24:
>> include/linux/bio.h:788:12: error: 'bio_integrity_setup' defined but not used [-Werror=unused-function]
static int bio_integrity_setup(struct bio *bio)
^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/bio_integrity_setup +788 include/linux/bio.h
782
783 static inline int bio_integrity_prep(struct bio *bio)
784 {
785 return 0;
786 }
787
> 788 static int bio_integrity_setup(struct bio *bio)
789 {
790 return 0;
791 }
---
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: 17530 bytes --]
next prev parent reply other threads:[~2017-03-31 22:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 13:49 [PATCH 0/8] block: T10/DIF Fixes and cleanups Dmitry Monakhov
2017-03-30 13:49 ` [PATCH 1/8] Guard bvec iteration logic Dmitry Monakhov
2017-03-31 8:21 ` Ming Lei
2017-03-30 13:49 ` [PATCH 2/8] bio-integrity: Do not allocate integrity context for bio w/o data Dmitry Monakhov
2017-03-30 13:49 ` [PATCH 3/8] bio-integrity: save original iterator for verify stage Dmitry Monakhov
2017-03-30 13:49 ` [PATCH 4/8] bio-integrity: bio_trim should truncate integrity vector accordingly Dmitry Monakhov
2017-03-30 13:49 ` [PATCH 5/8] bio-integrity: fix interface for bio_integrity_trim Dmitry Monakhov
2017-03-30 13:49 ` [PATCH 6/8] bio-integrity: add bio_integrity_setup helper Dmitry Monakhov
2017-03-31 22:15 ` kbuild test robot [this message]
2017-03-30 13:49 ` [PATCH 7/8] T10: Move opencoded contants to common header Dmitry Monakhov
2017-03-31 22:09 ` kbuild test robot
2017-03-30 13:49 ` [PATCH 8/8] tcm_fileio: Prevent information leak for short reads Dmitry Monakhov
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=201704010609.A37RyJqg%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dmonakhov@openvz.org \
--cc=kbuild-all@01.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.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