The fallback code for "unknown" architectures doesn't work on ARM
because for ARM (and a couple of other architectures) KBUILD_IMAGE
contains only the file name, not the full path. Having an explicit
rule also avoids printing the warning for unknown architectures.
Signed-off-by: Sascha Silbe <x-li...@infra-silbe.de>
---
scripts/package/buildtar | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/scripts/package/buildtar b/scripts/package/buildtar
index e046bff33589..cbcc4496c025 100755
--- a/scripts/package/buildtar
+++ b/scripts/package/buildtar
@@ -108,6 +108,11 @@ case "${ARCH}" in
cp -v -- "${objtree}/vmlinux"
"${tmpdir}/boot/vmlinux-${KERNELRELEASE}"
fi
;;
+ arm)
+ if [ -f "${objtree}/arch/${ARCH}/boot/${KBUILD_IMAGE}" ]; then
+ cp -v -- "${objtree}/arch/${ARCH}/boot/${KBUILD_IMAGE}"
"${tmpdir}/boot/${KBUILD_IMAGE}-${KERNELRELEASE}"
+ fi
+ ;;
*)
[ -f "${KBUILD_IMAGE}" ] && cp -v -- "${KBUILD_IMAGE}"
"${tmpdir}/boot/vmlinux-kbuild-${KERNELRELEASE}"
echo "" >&2
--
2.11.0
