[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200312083943.GA7278@alpha.franken.de>
Date: Thu, 12 Mar 2020 09:39:43 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: linux-mips@...r.kernel.org, Paul Burton <paulburton@...nel.org>,
kbuild-all@...ts.01.org,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
"sparclinux@...r.kernel.org, David S . Miller" <davem@...emloft.net>,
clang-built-linux <clang-built-linux@...glegroups.com>,
Al Viro <viro@...iv.linux.org.uk>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Ilie Halip <ilie.halip@...il.com>,
Nathan Chancellor <natechancellor@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Michal Marek <michal.lkml@...kovi.net>,
kbuild test robot <lkp@...el.com>
Subject: Re: [PATCH v2 2/2] kbuild: link lib-y objects to vmlinux forcibly
when CONFIG_MODULES=y
On Thu, Mar 12, 2020 at 03:12:28PM +0900, Masahiro Yamada wrote:
> I got the following report from 0-day bot.
> Please advise me how to fix it.
>
>
> I am not sure how multi-platform works in MIPS.
>
> The cavium-octeon platform has its own implementation
> of various functions.
>
> So, vmlinux links different library routines
> depending on whether CONFIG_CAVIUM_OCTEON_SOC, correct?
for cavium memcpy is directly linked in via octeon-memcpy.o, while for
every other platform it's coming from lib/lib.a(memcpy.o).
What have you changed, that this doesn't work anymore ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists