From: kbuild test robot <lkp@intel.com>
To: Brijesh Singh <brijesh.singh@amd.com>
Cc: kbuild-all@01.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas.lendacky@amd.com,
gary.hook@amd.com, herbert@gondor.apana.org.au,
davem@davemloft.net, Brijesh Singh <brijesh.singh@amd.com>
Subject: Re: [PATCH v2 2/3] crypto: ccp - Introduce the AMD Secure Processor device
Date: Thu, 6 Jul 2017 16:37:21 +0800 [thread overview]
Message-ID: <201707061641.wxDNmX4a%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170623160630.63292-3-brijesh.singh@amd.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Hi Brijesh,
[auto build test ERROR on cryptodev/master]
[also build test ERROR on next-20170705]
[cannot apply to v4.12]
[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/Brijesh-Singh/Introduce-AMD-Secure-Processor-device/20170625-064400
base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
config: x86_64-randconfig-x016-07060921 (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: "ccp_dev_resume" [drivers/crypto/ccp/ccp.ko] undefined!
>> ERROR: "ccp_dev_suspend" [drivers/crypto/ccp/ccp.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: 27067 bytes --]
next prev parent reply other threads:[~2017-07-06 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 16:06 [PATCH v2 0/3] Introduce " Brijesh Singh
2017-06-23 16:06 ` [PATCH v2 1/3] crypto: ccp - Use devres interface to allocate PCI/iomap and cleanup Brijesh Singh
2017-06-26 21:17 ` Tom Lendacky
2017-06-26 22:22 ` Brijesh Singh
2017-06-23 16:06 ` [PATCH v2 2/3] crypto: ccp - Introduce the AMD Secure Processor device Brijesh Singh
2017-06-28 17:47 ` Tom Lendacky
2017-06-28 19:39 ` Brijesh Singh
2017-06-28 19:53 ` Tom Lendacky
2017-06-28 20:26 ` Brijesh Singh
2017-06-28 20:30 ` Tom Lendacky
2017-07-06 8:37 ` kbuild test robot [this message]
2017-07-06 12:27 ` Brijesh Singh
2017-06-23 16:06 ` [PATCH v2 3/3] crypto: cpp - Abstract interrupt registeration Brijesh Singh
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=201707061641.wxDNmX4a%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=brijesh.singh@amd.com \
--cc=davem@davemloft.net \
--cc=gary.hook@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.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®