public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Meng Yu <yumeng18@huawei.com>,
	herbert@gondor.apana.org.au, davem@davemloft.net
Cc: kbuild-all@lists.01.org, linux-crypto@vger.kernel.org,
	xuzaibo@huawei.com, wangzhou1@hisilicon.com, yumeng18@huawei.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] crypto: hisilicon/hpre - add 'CURVE25519' algorithm
Date: Sun, 1 Nov 2020 11:54:43 +0800	[thread overview]
Message-ID: <202011011144.pcPd7kqn-lkp@intel.com> (raw)
In-Reply-To: <1604126068-29195-6-git-send-email-yumeng18@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

Hi Meng,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on cryptodev/master]
[also build test ERROR on crypto/master v5.10-rc1 next-20201030]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Meng-Yu/crypto-hisilicon-hpre-add-something-for-Kunpeng-930/20201031-143748
base:   https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/5bfec963e8d2806a362f1f9da490543d939baf26
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Meng-Yu/crypto-hisilicon-hpre-add-something-for-Kunpeng-930/20201031-143748
        git checkout 5bfec963e8d2806a362f1f9da490543d939baf26
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> ld: drivers/crypto/hisilicon/hpre/hpre_crypto.o:(.rodata+0x1860): multiple definition of `curve25519_null_point'; lib/crypto/curve25519-generic.o:(.rodata+0x40): first defined here

---
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: 76922 bytes --]

      reply	other threads:[~2020-11-01  3:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-31  6:34 [PATCH 0/5] crypto: hisilicon/hpre - add something for 'Kunpeng 930' Meng Yu
2020-10-31  6:34 ` [PATCH 1/5] crypto: hisilicon/hpre - add initial settings adapt to " Meng Yu
2020-10-31  6:34 ` [PATCH 2/5] crypto: hisilicon/hpre - add version adapt to new algorithms Meng Yu
2020-10-31  6:34 ` [PATCH 3/5] crypto: hisilicon/hpre - add algorithm type Meng Yu
2020-10-31  6:34 ` [PATCH 4/5] crypto: hisilicon/hpre - add 'ECDH' algorithm Meng Yu
2020-10-31  6:34 ` [PATCH 5/5] crypto: hisilicon/hpre - add 'CURVE25519' algorithm Meng Yu
2020-11-01  3:54   ` kernel test robot [this message]

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=202011011144.pcPd7kqn-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangzhou1@hisilicon.com \
    --cc=xuzaibo@huawei.com \
    --cc=yumeng18@huawei.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