All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Breno Leitao <leitao@debian.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH net-next v2 1/3] crypto: caam: Make CRYPTO_DEV_FSL_CAAM dependent of COMPILE_TEST
Date: Mon, 8 Jul 2024 11:33:59 +0800	[thread overview]
Message-ID: <202407081155.WRdTU82G-lkp@intel.com> (raw)
In-Reply-To: <20240628161450.2541367-2-leitao@debian.org>

Hi Breno,

kernel test robot noticed the following build errors:

[auto build test ERROR on net-next/main]

url:    https://github.com/intel-lab-lkp/linux/commits/Breno-Leitao/crypto-caam-Make-CRYPTO_DEV_FSL_CAAM-dependent-of-COMPILE_TEST/20240630-073726
base:   net-next/main
patch link:    https://lore.kernel.org/r/20240628161450.2541367-2-leitao%40debian.org
patch subject: [PATCH net-next v2 1/3] crypto: caam: Make CRYPTO_DEV_FSL_CAAM dependent of COMPILE_TEST
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240708/202407081155.WRdTU82G-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240708/202407081155.WRdTU82G-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407081155.WRdTU82G-lkp@intel.com/

All errors (new ones prefixed by >>):

   alpha-linux-ld: drivers/crypto/caam/jr.o: in function `caam_jr_init':
>> (.text+0x1938): undefined reference to `iowrite64be'
>> alpha-linux-ld: (.text+0x1944): undefined reference to `iowrite64be'
   alpha-linux-ld: (.text+0x19b4): undefined reference to `iowrite64be'
   alpha-linux-ld: (.text+0x19bc): undefined reference to `iowrite64be'

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2024-07-08  3:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 16:14 [PATCH net-next v2 0/3] crypto: caam: Unembed net_dev Breno Leitao
2024-06-28 16:14 ` [PATCH net-next v2 1/3] crypto: caam: Make CRYPTO_DEV_FSL_CAAM dependent of COMPILE_TEST Breno Leitao
2024-07-01  5:48   ` kernel test robot
2024-07-01 20:55     ` Jakub Kicinski
2024-07-02 17:53     ` Breno Leitao
2024-07-08  3:33   ` kernel test robot [this message]
2024-06-28 16:14 ` [PATCH net-next v2 2/3] crypto: caam: Unembed net_dev structure from qi Breno Leitao
2024-06-28 16:14 ` [PATCH net-next v2 3/3] crypto: caam: Unembed net_dev structure in dpaa2 Breno Leitao

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=202407081155.WRdTU82G-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=leitao@debian.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.