From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [linux-next:master 10400/10976] arch/arm/vfp/entry.S:27: undefined reference to `vfp_entry'
Date: Wed, 12 Apr 2023 16:50:33 +0800 [thread overview]
Message-ID: <202304121606.ltRFyuij-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 7d8214bba44c1aa6a75921a09a691945d26a8d43
commit: 62fa0c124d5ff1d1b1fab988ed4ef0e82e3ece16 [10400/10976] ARM: 9294/1: vfp: Fix broken softirq handling with instrumentation enabled
config: arm-keystone_defconfig (https://download.01.org/0day-ci/archive/20230412/202304121606.ltRFyuij-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.1.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=62fa0c124d5ff1d1b1fab988ed4ef0e82e3ece16
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 62fa0c124d5ff1d1b1fab988ed4ef0e82e3ece16
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304121606.ltRFyuij-lkp@intel.com/
All errors (new ones prefixed by >>):
arm-linux-gnueabi-ld: arch/arm/vfp/entry.o: in function `do_vfp':
>> arch/arm/vfp/entry.S:27: undefined reference to `vfp_entry'
vim +27 arch/arm/vfp/entry.S
14
15 @ VFP entry point.
16 @
17 @ r0 = instruction opcode (32-bit ARM or two 16-bit Thumb)
18 @ r2 = PC value to resume execution after successful emulation
19 @ r9 = normal "successful" return address
20 @ r10 = this threads thread_info structure
21 @ lr = unrecognised instruction return address
22 @ IRQs enabled.
23 @
24 ENTRY(do_vfp)
25 mov r1, r10
26 mov r3, r9
> 27 b vfp_entry
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-04-12 8:51 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=202304121606.ltRFyuij-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
/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.