From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, agk@redhat.com, snitzer@redhat.com,
dm-devel@redhat.com, shli@kernel.org, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, Bongkyu Kim <bongkyu.kim@lge.com>
Subject: Re: [PATCH] dm verity: deferred hash checking for restart/logging mode
Date: Mon, 24 Apr 2017 17:58:20 +0800 [thread overview]
Message-ID: <201704241743.rli5VH6D%fengguang.wu@intel.com> (raw)
In-Reply-To: <1493019260-43938-1-git-send-email-bongkyu.kim@lge.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Hi Bongkyu,
[auto build test ERROR on dm/for-next]
[also build test ERROR on v4.11-rc8 next-20170421]
[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/Bongkyu-Kim/dm-verity-deferred-hash-checking-for-restart-logging-mode/20170424-154859
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> ERROR: "free_io" [drivers/md/dm-verity.ko] undefined!
---
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: 38849 bytes --]
prev parent reply other threads:[~2017-04-24 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 7:34 [PATCH] dm verity: deferred hash checking for restart/logging mode Bongkyu Kim
2017-04-24 8:05 ` Milan Broz
2017-04-24 15:54 ` Sami Tolvanen
2017-04-24 9:58 ` kbuild test robot [this message]
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=201704241743.rli5VH6D%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=agk@redhat.com \
--cc=bongkyu.kim@lge.com \
--cc=dm-devel@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=snitzer@redhat.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