From: Nelson Chu <nelson@rivosinc.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: schwab@suse.de, binutils@sourceware.org
Subject: Re: [PATCH] Add basic support for RISC-V 64-bit EFI objects
Date: Mon, 28 Aug 2023 10:03:49 +0800 [thread overview]
Message-ID: <CAPpQWtDRqZbbAUFjqegQhCRgegWy58R=NVzQM03YqM+jvh=hXw@mail.gmail.com> (raw)
In-Reply-To: <mhng-ca150425-b1c1-4cb0-a83c-e499b801ad92@palmer-ri-x1c9>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On Fri, Aug 25, 2023 at 9:26 PM Palmer Dabbelt <palmer@dabbelt.com> wrote:
> On Thu, 24 Aug 2023 19:15:32 PDT (-0700), nelson@rivosinc.com wrote:
> > Passed the binutils regression, and the pei-riscv64 testcase is also
> > passed. I don't familiar with the COFF stuff, but at least the support
> of
> > objdump and objcopy seems to be working, that's what I can check the most
> > currently. Hope this helps before any expert comments appear ;)
>
> So you think it's ready to merge, or did you want to look closer?
>
At least it should be safe to merge since regressions are passed, and
current features shouldn't be affected. So if no one objected after a
while, it should merge.
Nelson
next prev parent reply other threads:[~2023-08-28 2:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 14:18 Andreas Schwab
2023-08-09 1:54 ` Palmer Dabbelt
2023-08-09 8:10 ` Andreas Schwab
2023-08-25 2:15 ` Nelson Chu
2023-08-25 13:26 ` Palmer Dabbelt
2023-08-28 2:03 ` Nelson Chu [this message]
2023-09-06 15:40 ` Palmer Dabbelt
2023-09-06 20:01 ` Peter Jones
2023-09-06 20:01 ` [PATCH] Handle "efi-app-riscv64" and similar targets in objcopy Peter Jones
2023-12-04 17:16 ` Palmer Dabbelt
2023-12-05 6:45 ` Nelson Chu
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='CAPpQWtDRqZbbAUFjqegQhCRgegWy58R=NVzQM03YqM+jvh=hXw@mail.gmail.com' \
--to=nelson@rivosinc.com \
--cc=binutils@sourceware.org \
--cc=palmer@dabbelt.com \
--cc=schwab@suse.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 read-only IMAP folder(s) and NNTP newsgroup(s).