From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Jens Axboe" <axboe@kernel.dk>
Subject: Re: arm-linux-gnueabi-ld: error: .btf.vmlinux.bin.o is already in final BE8 format
Date: Thu, 14 Sep 2023 07:08:14 +0200 [thread overview]
Message-ID: <5cace191-31f6-4aa5-8b19-aa6c1f2db7e6@app.fastmail.com> (raw)
In-Reply-To: <202309141131.pNe5J6HH-lkp@intel.com>
On Thu, Sep 14, 2023, at 05:45, kernel test robot wrote:
>
> 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
It's a completely unrelated issue at the link stage that gets
exposed by fixing the other bug. I don't see this in my
randconfig builds right now, so I probably have a workaround for
it somewhere, but I can't find it.
Arnd
next prev parent reply other threads:[~2023-09-14 5:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 3:45 kernel test robot
2023-09-14 5:08 ` Arnd Bergmann [this message]
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
2022-09-10 16:50 kernel test robot
2022-07-16 23:20 kernel test robot
2022-06-11 21:00 kernel test robot
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=5cace191-31f6-4aa5-8b19-aa6c1f2db7e6@app.fastmail.com \
--to=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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
all inboxes | Powered by JetHome®