From: Calvin Owens <calvin@wbinvd.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-kbuild@vger.kernel.org
Subject: [PATCH v2] kbuild: buildtar: Add explicit 32-bit arm support
Date: Fri, 12 Apr 2024 12:26:06 -0700 [thread overview]
Message-ID: <ZhmKzqxHXaSZmXee@mozart.vkv.me> (raw)
In-Reply-To: <ZhcZCwMmANQS39s2@mozart.vkv.me>
Implement buildtar for 32-bit arm, so the zImage (or xipimage) appears
at boot/vmlinuz-$foo, rather than at boot/vmlinux-kbuild-$foo, matching
the structure of the tar-pkg on arm64 and other architectures.
Link: https://lore.kernel.org/all/e7c14a0d329e28bdcda21376b54a43c85a4aaf3f.1712682861.git.calvin@wbinvd.org/
Signed-off-by: Calvin Owens <calvin@wbinvd.org>
---
scripts/package/buildtar | 3 +++
1 file changed, 3 insertions(+)
diff --git a/scripts/package/buildtar b/scripts/package/buildtar
index 72c91a1b832f..86035c990aec 100755
--- a/scripts/package/buildtar
+++ b/scripts/package/buildtar
@@ -101,6 +101,9 @@ case "${ARCH}" in
fi
done
;;
+ arm)
+ [ -f "${KBUILD_IMAGE}" ] && cp -v -- "${KBUILD_IMAGE}" "${tmpdir}/boot/vmlinuz-${KERNELRELEASE}"
+ ;;
*)
[ -f "${KBUILD_IMAGE}" ] && cp -v -- "${KBUILD_IMAGE}" "${tmpdir}/boot/vmlinux-kbuild-${KERNELRELEASE}"
echo "" >&2
--
2.39.2
next prev parent reply other threads:[~2024-04-12 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 17:17 [PATCH] kbuild: buildtar: Add " Calvin Owens
2024-04-10 17:04 ` Nathan Chancellor
2024-04-10 22:56 ` Calvin Owens
2024-04-12 19:23 ` Calvin Owens
2024-04-12 21:47 ` Nathan Chancellor
2024-04-12 19:26 ` Calvin Owens [this message]
2024-04-12 21:48 ` [PATCH v2] kbuild: buildtar: Add explicit 32-bit " Nathan Chancellor
2024-06-21 2:25 ` [RESEND PATCH " Calvin Owens
2024-06-21 14:55 ` Nathan Chancellor
2024-06-22 2:55 ` Calvin Owens
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=ZhmKzqxHXaSZmXee@mozart.vkv.me \
--to=calvin@wbinvd.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
/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®