From: Palmer Dabbelt <palmer@dabbelt.com>
To: me@carlosedp.com
Cc: david.abdurachmanov@sifive.com, me@carlosedp.com,
masahiroy@kernel.org, michal.lkml@markovi.net,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] kbuild: buildtar: add riscv support
Date: Mon, 29 Mar 2021 22:06:31 -0700 (PDT) [thread overview]
Message-ID: <mhng-6e97a94b-b3a1-4bdb-aa0b-30f44ec3d2fb@palmerdabbelt-glaptop> (raw)
In-Reply-To: <20210316160242.61712-1-me@carlosedp.com>
On Tue, 16 Mar 2021 09:02:43 PDT (-0700), me@carlosedp.com wrote:
> Make 'make tar-pkg' and 'tarbz2-pkg' work on riscv.
>
> Signed-off-by: Carlos de Paula <me@carlosedp.com>
> ---
> scripts/package/buildtar | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/scripts/package/buildtar b/scripts/package/buildtar
> index 936198a90477..221aa7df008d 100755
> --- a/scripts/package/buildtar
> +++ b/scripts/package/buildtar
> @@ -123,10 +123,18 @@ case "${ARCH}" in
> cp -v -- "${objtree}/arch/arm64/boot/${i}" "${tmpdir}/boot/vmlinuz-${KERNELRELEASE}"
> break
> fi
> done
> ;;
> + riscv)
> + for i in Image.bz2 Image.gz Image; do
> + if [ -f "${objtree}/arch/riscv/boot/${i}" ] ; then
> + cp -v -- "${objtree}/arch/riscv/boot/${i}" "${tmpdir}/boot/vmlinux-${KERNELRELEASE}"
> + break
> + fi
> + done
> + ;;
> *)
> [ -f "${KBUILD_IMAGE}" ] && cp -v -- "${KBUILD_IMAGE}" "${tmpdir}/boot/vmlinux-kbuild-${KERNELRELEASE}"
> echo "" >&2
> echo '** ** ** WARNING ** ** **' >&2
> echo "" >&2
Thanks, this is on for-next.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2021-03-30 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 16:02 [PATCH] kbuild: buildtar: add riscv support Carlos de Paula
2021-03-30 5:06 ` Palmer Dabbelt [this message]
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=mhng-6e97a94b-b3a1-4bdb-aa0b-30f44ec3d2fb@palmerdabbelt-glaptop \
--to=palmer@dabbelt.com \
--cc=aou@eecs.berkeley.edu \
--cc=david.abdurachmanov@sifive.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=me@carlosedp.com \
--cc=michal.lkml@markovi.net \
--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).