From: kernel test robot <lkp@intel.com>
To: Ben Hutchings <bwh@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
YunQiang Su <syq@debian.org>
Subject: arch/mips/boot/compressed/decompress.c:undefined reference to `ftrace_likely_update'
Date: Fri, 5 Jun 2020 07:43:52 +0800 [thread overview]
Message-ID: <202006050749.1DK4QNHZ%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1814 bytes --]
Hi Ben,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 15a2bc4dbb9cfed1c661a657fcb10798150b7598
commit: f39293fd37fff74c531b7a52d0459cc77db85e7f MIPS: Fix exception handler memcpy()
date: 12 days ago
config: mips-randconfig-s031-20200604 (attached as .config)
compiler: mipsel-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-246-g41f651b4-dirty
git checkout f39293fd37fff74c531b7a52d0459cc77db85e7f
# save the attached .config to linux build tree
make W=1 C=1 ARCH=mips CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
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 >>, old ones prefixed by <<):
mipsel-linux-ld: arch/mips/boot/compressed/decompress.o: in function `lzo1x_decompress_safe':
>> arch/mips/boot/compressed/decompress.c:(.text+0x90): undefined reference to `ftrace_likely_update'
>> mipsel-linux-ld: arch/mips/boot/compressed/decompress.c:(.text+0xb0): undefined reference to `ftrace_likely_update'
mipsel-linux-ld: arch/mips/boot/compressed/decompress.c:(.text+0x140): undefined reference to `ftrace_likely_update'
mipsel-linux-ld: arch/mips/boot/compressed/decompress.c:(.text+0x194): undefined reference to `ftrace_likely_update'
mipsel-linux-ld: arch/mips/boot/compressed/decompress.c:(.text+0x1b4): undefined reference to `ftrace_likely_update'
mipsel-linux-ld: arch/mips/boot/compressed/decompress.o:arch/mips/boot/compressed/decompress.c:(.text+0x1e4): more undefined references to `ftrace_likely_update' follow
---
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: 27262 bytes --]
reply other threads:[~2020-06-04 23:45 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=202006050749.1DK4QNHZ%lkp@intel.com \
--to=lkp@intel.com \
--cc=bwh@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syq@debian.org \
--cc=tsbogend@alpha.franken.de \
/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®