From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>
Subject: arm-linux-gnueabi-ld: error: .btf.vmlinux.bin.o is already in final BE8 format
Date: Thu, 14 Sep 2023 11:45:17 +0800 [thread overview]
Message-ID: <202309141131.pNe5J6HH-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: aed8aee11130a954356200afa3f1b8753e8a9482
commit: 5f2779dfa7b8cc7dfd4a1b6586d86e0d193266f3 blk-iocost: avoid 64-bit division in ioc_timer_fn
date: 8 months ago
config: arm-randconfig-002-20230914 (https://download.01.org/0day-ci/archive/20230914/202309141131.pNe5J6HH-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230914/202309141131.pNe5J6HH-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/202309141131.pNe5J6HH-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arm-linux-gnueabi-ld: error: .btf.vmlinux.bin.o is already in final BE8 format
arm-linux-gnueabi-ld: failed to merge target specific data of file .btf.vmlinux.bin.o
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-09-14 3:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 3:45 kernel test robot [this message]
2023-09-14 5:08 ` arm-linux-gnueabi-ld: error: .btf.vmlinux.bin.o is already in final BE8 format Arnd Bergmann
2023-09-14 10:11 ` Philip Li
2023-09-14 10:16 ` Philip Li
-- strict thread matches above, loose matches on Subject: below --
2023-03-29 17:54 kernel test robot
2023-01-31 0:50 kernel test robot
2022-11-11 22:16 kernel test robot
2022-10-29 20:59 kernel test robot
[not found] <202206120438.Un6Wq4N0-lkp@intel.com>
2022-06-14 16:20 ` Arnd Bergmann
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=202309141131.pNe5J6HH-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.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 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).