linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aurabindo Jayamohanan <mail@aurabindo.in>
To: Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@sifive.com>,
	Albert Ou <aou@eecs.berkeley.edu>
Cc: "linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>
Subject: [RFC] buildtar: add case for riscv architecture
Date: Wed, 11 Sep 2019 07:07:06 +0000	[thread overview]
Message-ID: <NwVOGH2ZdDQaDK35QUy7y8GS__G8IYSIUUIBAJsimZq5BgvI3SzLS3uY6fV7Pgppq-RTRHzpT-8KrsLjDN74CPWwHTCWoSgHkGbeJNvyS30=@aurabindo.in> (raw)

[-- Attachment #1: Type: text/plain, Size: 240 bytes --]

Hi,

I would like to know if something extra needs to be done other than copying compressed kernel image, when making tar package for riscv architecture. Please see the attached patch.

--

Thanks and Regards,
Aurabindo Jayamohanan

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-buildtar-add-riscv-case.patch --]
[-- Type: text/x-patch; name="0001-buildtar-add-riscv-case.patch", Size: 1169 bytes --]

From 86feb93c62daa61314df0bbe1a11272c23b1eadb Mon Sep 17 00:00:00 2001
From: Aurabindo Jayamohanan <mail@aurabindo.in>
Date: Thu, 5 Sep 2019 12:52:45 +0530
Subject: [PATCH] buildtar: add riscv case

Copy compressed kernel image into tarball root. Similar
action for both arm64 and riscv architectures.

Signed-off-by: Aurabindo Jayamohanan <mail@aurabindo.in>
---
 scripts/package/buildtar | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/scripts/package/buildtar b/scripts/package/buildtar
index 2f66c81e4021..388d0fcbe8c2 100755
--- a/scripts/package/buildtar
+++ b/scripts/package/buildtar
@@ -105,10 +105,10 @@ case "${ARCH}" in
 			cp -v -- "${objtree}/vmlinux" "${tmpdir}/boot/vmlinux-${KERNELRELEASE}"
 		fi
 		;;
-	arm64)
+	arm64|riscv)
 		for i in Image.bz2 Image.gz Image.lz4 Image.lzma Image.lzo ; do
-			if [ -f "${objtree}/arch/arm64/boot/${i}" ] ; then
-				cp -v -- "${objtree}/arch/arm64/boot/${i}" "${tmpdir}/boot/vmlinuz-${KERNELRELEASE}"
+			if [ -f "${objtree}/arch/${ARCH}/boot/${i}" ] ; then
+				cp -v -- "${objtree}/arch/${ARCH}/boot/${i}" "${tmpdir}/boot/vmlinuz-${KERNELRELEASE}"
 				break
 			fi
 		done
-- 
2.23.0


             reply	other threads:[~2019-09-11  7:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  7:07 Aurabindo Jayamohanan [this message]
2019-09-11  9:05 ` [RFC] buildtar: add case for riscv architecture Troy Benjegerdes
2019-09-11 12:54   ` Aurabindo Jayamohanan
2019-09-14 12:59     ` Palmer Dabbelt
2019-09-14 13:05       ` Anup Patel
2019-09-14 19:27         ` Palmer Dabbelt
2019-09-17  9:35           ` Aurabindo Jayamohanan
2019-09-20 22:40             ` Palmer Dabbelt

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='NwVOGH2ZdDQaDK35QUy7y8GS__G8IYSIUUIBAJsimZq5BgvI3SzLS3uY6fV7Pgppq-RTRHzpT-8KrsLjDN74CPWwHTCWoSgHkGbeJNvyS30=@aurabindo.in' \
    --to=mail@aurabindo.in \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@sifive.com \
    /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).