From: kbuild test robot <fengguang.wu@intel.com>
To: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Cc: kbuild-all@01.org, linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: [cryptodev:master 41/47] ERROR: "crypto_acomp_scomp_free_ctx" [crypto/acompress.ko] undefined!
Date: Wed, 26 Oct 2016 08:47:16 +0800 [thread overview]
Message-ID: <201610260803.GIBxWXo3%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
head: d7db7a882debaffc78f91aabedee973aa1f73390
commit: 1ab53a77b772bf7369464a0e4fa6fd6499acf8f1 [41/47] crypto: acomp - add driver-side scomp interface
config: x86_64-randconfig-s4-10260656 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout 1ab53a77b772bf7369464a0e4fa6fd6499acf8f1
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> ERROR: "crypto_acomp_scomp_free_ctx" [crypto/acompress.ko] undefined!
>> ERROR: "crypto_acomp_scomp_alloc_ctx" [crypto/acompress.ko] undefined!
>> ERROR: "crypto_init_scomp_ops_async" [crypto/acompress.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: 19304 bytes --]
next reply other threads:[~2016-10-26 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 0:47 kbuild test robot [this message]
2016-10-26 9:56 ` [cryptodev:master 41/47] ERROR: "crypto_acomp_scomp_free_ctx" [crypto/acompress.ko] undefined! Giovanni Cabiddu
2016-11-01 0:44 ` Herbert Xu
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=201610260803.GIBxWXo3%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=linux-crypto@vger.kernel.org \
/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