From: Paul Walmsley <paul.walmsley@sifive.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"trini@konsulko.com" <trini@konsulko.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <anup@brainfault.org>,
Palmer Dabbelt <palmer@sifive.com>, Zong Li <zong@andestech.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"merker@debian.org" <merker@debian.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [v2 PATCH] RISC-V: Add a PE/COFF compliant Image header.
Date: Thu, 23 May 2019 11:45:57 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1905231145250.31734@viisi.sifive.com> (raw)
In-Reply-To: <d7ef1d58-2c3f-ef58-b6aa-bb7ccfe162f6@wdc.com>
On Thu, 23 May 2019, Atish Patra wrote:
> I have sent out a v3 incorporating most of your suggestions. If ARM
> maintainers agree, we can move both the headers to a common place.
>
> Just FYI: Marek also suggested to add unified support Image.gz for both U-Boot
> & RISC-V in U-Boot. I am working on that as well.
Great - thanks very much.
- Paul
next prev parent reply other threads:[~2019-05-23 18:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 19:56 Atish Patra
2019-05-05 0:37 ` Karsten Merker
2019-05-11 20:57 ` Karsten Merker
2019-05-13 22:31 ` Paul Walmsley
2019-05-13 23:18 ` Atish Patra
2019-05-14 0:09 ` Paul Walmsley
2019-05-14 0:34 ` Atish Patra
2019-05-14 0:39 ` Paul Walmsley
2019-05-14 1:13 ` Atish Patra
2019-05-16 16:20 ` Paul Walmsley
2019-05-23 18:35 ` Atish Patra
2019-05-23 18:45 ` Paul Walmsley [this message]
2019-05-17 17:39 ` Paul Walmsley
2019-05-17 19:00 ` Atish Patra
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=alpine.DEB.2.21.9999.1905231145250.31734@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=merker@debian.org \
--cc=palmer@sifive.com \
--cc=trini@konsulko.com \
--cc=will.deacon@arm.com \
--cc=zong@andestech.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
all inboxes | Powered by JetHome®