From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
kernel test robot <lkp@intel.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org
Subject: [PATCH] mips: CONFIG_KERNEL_LZ4 needs obj/bswapsi.o
Date: Sun, 4 Jul 2021 16:02:38 -0700 [thread overview]
Message-ID: <20210704230238.577-1-rdunlap@infradead.org> (raw)
Add obj/bswapsi.o for CONFIG_KERNEL_LZ4 to fix undefined references
during linking.
mips64-linux-ld: arch/mips/boot/compressed/decompress.o: in function `decompress_kernel':
decompress.c:(.text+0x34e0): undefined reference to `__bswapsi2'
mips64-linux-ld: decompress.c:(.text+0x3504): undefined reference to `__bswapsi2'
mips64-linux-ld: decompress.c:(.text+0x3530): undefined reference to `__bswapsi2'
#Fixes: d0nt0110kn0w ("I couldn't find where __bswapsi2 is used.")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org
---
arch/mips/boot/compressed/Makefile | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20210701.orig/arch/mips/boot/compressed/Makefile
+++ linux-next-20210701/arch/mips/boot/compressed/Makefile
@@ -55,6 +55,7 @@ $(obj)/uart-ath79.c: $(srctree)/arch/mip
$(call cmd,shipped)
vmlinuzobjs-$(CONFIG_KERNEL_XZ) += $(obj)/ashldi3.o $(obj)/bswapsi.o
+vmlinuzobjs-$(CONFIG_KERNEL_LZ4) += $(obj)/bswapsi.o
extra-y += ashldi3.c
$(obj)/ashldi3.c: $(obj)/%.c: $(srctree)/lib/%.c FORCE
next reply other threads:[~2021-07-04 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 23:02 Randy Dunlap [this message]
2021-07-05 15:09 ` [PATCH] mips: CONFIG_KERNEL_LZ4 needs obj/bswapsi.o Thomas Bogendoerfer
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=20210704230238.577-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).