From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 2722/12985] hpre_crypto.c:undefined reference to `crypto_ecdh_decode_key'
Date: Fri, 16 Apr 2021 03:27:28 +0800 [thread overview]
Message-ID: <202104160323.LheVi7Wd-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 1216f02e46a46aad2a9c1c3bb29032f0b42eedac
commit: 05e7b906aa7c8690906135dc86ab0fc12ee37481 [2722/12985] crypto: hisilicon/hpre - add 'ECDH' algorithm
config: x86_64-randconfig-c002-20210415 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=05e7b906aa7c8690906135dc86ab0fc12ee37481
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 05e7b906aa7c8690906135dc86ab0fc12ee37481
# save the attached .config to linux build tree
make W=1 W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD 1216f02e46a46aad2a9c1c3bb29032f0b42eedac builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
ld: drivers/crypto/hisilicon/hpre/hpre_crypto.o: in function `hpre_ecdh_set_secret':
>> hpre_crypto.c:(.text+0x5733): undefined reference to `crypto_ecdh_decode_key'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 45250 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Meng Yu <yumeng18@huawei.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Zaibo Xu <xuzaibo@huawei.com>
Subject: [linux-next:master 2722/12985] hpre_crypto.c:undefined reference to `crypto_ecdh_decode_key'
Date: Fri, 16 Apr 2021 03:27:28 +0800 [thread overview]
Message-ID: <202104160323.LheVi7Wd-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 1216f02e46a46aad2a9c1c3bb29032f0b42eedac
commit: 05e7b906aa7c8690906135dc86ab0fc12ee37481 [2722/12985] crypto: hisilicon/hpre - add 'ECDH' algorithm
config: x86_64-randconfig-c002-20210415 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=05e7b906aa7c8690906135dc86ab0fc12ee37481
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 05e7b906aa7c8690906135dc86ab0fc12ee37481
# save the attached .config to linux build tree
make W=1 W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD 1216f02e46a46aad2a9c1c3bb29032f0b42eedac builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
ld: drivers/crypto/hisilicon/hpre/hpre_crypto.o: in function `hpre_ecdh_set_secret':
>> hpre_crypto.c:(.text+0x5733): undefined reference to `crypto_ecdh_decode_key'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 45250 bytes --]
next reply other threads:[~2021-04-15 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 19:27 kernel test robot [this message]
2021-04-15 19:27 ` [linux-next:master 2722/12985] hpre_crypto.c:undefined reference to `crypto_ecdh_decode_key' kernel test robot
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=202104160323.LheVi7Wd-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.