From: "John Thomson" <git@johnthomson.fastmail.com.au>
To: linux-mips@vger.kernel.org
Cc: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mips: boot compressed: add support for vlinuz ELF DTB
Date: Sat, 17 Oct 2020 22:13:55 +0000 [thread overview]
Message-ID: <33a813e4-f92c-4d34-a4d7-9d80203aa2fa@www.fastmail.com> (raw)
In-Reply-To: <20201015201100.4130-2-git@johnthomson.fastmail.com.au>
I think it would be safer to make these changes by adding a different boot/compressed target: vmlinuz.elf?
So that this would not break kernel build cases where both a normal RAW_APPENDED_DTB zImage is wanted, and additionally an ELF boot vmlinuz.elf.
--
John Thomson
prev parent reply other threads:[~2020-10-17 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 20:10 [PATCH 1/2] mips: boot compressed: preprocess linker script John Thomson
2020-10-15 20:11 ` [PATCH 2/2] mips: boot compressed: add support for vlinuz ELF DTB John Thomson
2020-10-17 22:13 ` John Thomson [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=33a813e4-f92c-4d34-a4d7-9d80203aa2fa@www.fastmail.com \
--to=git@johnthomson.fastmail.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).