From: kbuild test robot <fengguang.wu@intel.com>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: kbuild-all@01.org, linux-unionfs@vger.kernel.org
Subject: [miklos-vfs:readlink 17/17] ERROR: "vfs_get_link" [fs/ecryptfs/ecryptfs.ko] undefined!
Date: Tue, 13 Sep 2016 09:30:13 +0800 [thread overview]
Message-ID: <201609130907.hBsvb15t%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git readlink
head: 08eed16ecf8c5061bbd5833411c6933728ff422f
commit: 08eed16ecf8c5061bbd5833411c6933728ff422f [17/17] ecryptfs: use vfs_get_link()
config: i386-randconfig-s0-201637 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
git checkout 08eed16ecf8c5061bbd5833411c6933728ff422f
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> ERROR: "vfs_get_link" [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: 26571 bytes --]
reply other threads:[~2016-09-12 17:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201609130907.hBsvb15t%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mszeredi@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;
as well as URLs for NNTP newsgroup(s).