buildtar warns when an architecture doesn't have an explicit rule on
what files to copy, even when the generic rule works just fine. Add a
rule for ARM that does the same as the explicit rule, but avoids the
warning.
Signed-off-by: Sascha Silbe <x-linux@xxxxxxxxxxxxxx>
---
v1→v2: rebased on top of todays linus master, including commit 152e6744ebfc
Not duplicating the rule would have been nice from a maintenance point
of view, but doesn't fit the current code structure very well. It also
avoids breakage if the generic rule ever gets adjusted to something
else that doesn't work for ARM.
scripts/package/buildtar | 3 +++
1 file changed, 3 insertions(+)
diff --git a/scripts/package/buildtar b/scripts/package/buildtar
index e046bff33589..ea84ba67619b 100755
--- a/scripts/package/buildtar
+++ b/scripts/package/buildtar
@@ -108,6 +108,9 @@ case "${ARCH}" in
cp -v -- "${objtree}/vmlinux" "${tmpdir}/boot/vmlinux-${KERNELRELEASE}"
fi
;;
+ arm)
+ [ -f "${KBUILD_IMAGE}" ] && cp -v -- "${KBUILD_IMAGE}" "${tmpdir}/boot/vmlinux-kbuild-${KERNELRELEASE}"
+ ;;
*)
[ -f "${KBUILD_IMAGE}" ] && cp -v -- "${KBUILD_IMAGE}" "${tmpdir}/boot/vmlinux-kbuild-${KERNELRELEASE}"
echo "" >&2
--
2.11.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
