From: kbuild test robot <lkp@intel.com>
To: Andrey Markovytch <andreym@codeaurora.org>
Cc: kbuild-all@01.org, tyhicks@canonical.com,
ecryptfs@vger.kernel.org, linaz@codeaurora.org,
Andrey Markovytch <andreym@codeaurora.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] eCryptfs: enhancing eCryptfs to be used with external crypto engine
Date: Sun, 8 Nov 2015 17:31:13 +0800 [thread overview]
Message-ID: <201511081718.vd0cydJO%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446970468-21434-1-git-send-email-andreym@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
Hi Andrey,
[auto build test ERROR on: v4.3-rc7]
[also build test ERROR on: next-20151106]
url: https://github.com/0day-ci/linux/commits/Andrey-Markovytch/eCryptfs-enhancing-eCryptfs-to-be-used-with-external-crypto-engine/20151108-161722
config: x86_64-randconfig-s0-11081650 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> ERROR: "__iget" [fs/ecryptfs/ecryptfs.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/octet-stream, Size: 23599 bytes --]
next prev parent reply other threads:[~2015-11-08 9:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 8:14 Andrey Markovytch
2015-11-08 9:31 ` kbuild test robot [this message]
2015-11-08 11:06 ` kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2015-11-23 20:42 andreym
2015-11-08 8:10 Andrey Markovytch
2015-11-08 9:26 ` Christoph Hellwig
2015-11-11 14:06 ` andreym
2015-11-09 17:55 ` Tyler Hicks
2015-11-09 20:56 ` andreym
2015-11-09 21:05 ` Tyler Hicks
2015-11-10 15:20 ` andreym
2015-11-10 15:27 ` andreym
2015-11-10 22:18 ` Tyler Hicks
2015-11-11 12:03 ` andreym
2015-11-11 20:55 ` Michael Halcrow
2015-11-12 20:23 ` andreym
2015-11-23 20:14 ` andreym
2015-11-09 22:17 ` Michael Halcrow
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=201511081718.vd0cydJO%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=andreym@codeaurora.org \
--cc=ecryptfs@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=linaz@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tyhicks@canonical.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
all inboxes | Powered by JetHome®