linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 1073/14055] mipsel-linux-ld: decompress.c:(.text.decompress_kernel+0x160): undefined reference to `__bswapsi2'
Date: Wed, 30 Jun 2021 13:26:10 +0800	[thread overview]
Message-ID: <202106301304.gz2wVY9w-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   73748627df83aab934c81332ca83a44ab8c7b3e3
commit: 0652035a57945e14e611dafae2ec5b46a05bc1d1 [1073/14055] asm-generic: unaligned: remove byteshift helpers
config: mips-randconfig-r003-20210628 (attached as .config)
compiler: mipsel-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=0652035a57945e14e611dafae2ec5b46a05bc1d1
        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 0652035a57945e14e611dafae2ec5b46a05bc1d1
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross O=build_dir ARCH=mips SHELL=/bin/bash

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 >>):

   mipsel-linux-ld: arch/mips/boot/compressed/decompress.o: in function `lzo1x_decompress_safe':
   decompress.c:(.text.lzo1x_decompress_safe+0x5c): undefined reference to `ftrace_likely_update'
   mipsel-linux-ld: decompress.c:(.text.lzo1x_decompress_safe+0x7c): undefined reference to `ftrace_likely_update'
   mipsel-linux-ld: decompress.c:(.text.lzo1x_decompress_safe+0xa8): undefined reference to `ftrace_likely_update'
   mipsel-linux-ld: decompress.c:(.text.lzo1x_decompress_safe+0x118): undefined reference to `ftrace_likely_update'
   mipsel-linux-ld: decompress.c:(.text.lzo1x_decompress_safe+0x164): undefined reference to `ftrace_likely_update'
   mipsel-linux-ld: arch/mips/boot/compressed/decompress.o:decompress.c:(.text.lzo1x_decompress_safe+0x1b0): more undefined references to `ftrace_likely_update' follow
   mipsel-linux-ld: arch/mips/boot/compressed/decompress.o: in function `decompress_kernel':
   decompress.c:(.text.decompress_kernel+0xd4): undefined reference to `__bswapsi2'
>> mipsel-linux-ld: decompress.c:(.text.decompress_kernel+0x160): undefined reference to `__bswapsi2'
   mipsel-linux-ld: decompress.c:(.text.decompress_kernel+0x1a4): undefined reference to `__bswapsi2'
>> mipsel-linux-ld: decompress.c:(.text.decompress_kernel+0x1e8): undefined reference to `ftrace_likely_update'

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

                 reply	other threads:[~2021-06-30  5:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202106301304.gz2wVY9w-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=arnd@arndb.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).