From: Palmer Dabbelt <palmer@dabbelt.com>
To: jeffreyalaw@gmail.com
Cc: christoph.muellner@vrull.eu, binutils@sourceware.org,
nelson@rivosinc.com, Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
philipp.tomsich@vrull.eu, jbeulich@suse.com,
Kito Cheng <kito.cheng@gmail.com>,
research_trasio@irq.a4lg.com
Subject: Re: [RFC PATCH v5] RISC-V: Add support for the Zfa extension
Date: Thu, 29 Jun 2023 09:12:28 -0700 (PDT) [thread overview]
Message-ID: <mhng-3d2267d0-e22b-4854-b92a-60a635033230@palmer-ri-x1c9> (raw)
In-Reply-To: <801ab9b8-a60c-ef18-de16-43284d790cdd@gmail.com>
On Thu, 29 Jun 2023 09:03:58 PDT (-0700), jeffreyalaw@gmail.com wrote:
>
>
> On 6/29/23 09:52, Palmer Dabbelt wrote:
>
>>
>> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>>
>> Presumably someone's actually looked at the code? If not I can look
>> over it...
> I've looked at it earlier. But I'll go over it again.
Thanks. If it looks good and passes the tests without any substantive
changes then feel free to commit it, any problems should be pretty
self-contained.
>
>
>>
>> Historically we've just kept whatever is released as a compatibility
>> mechanism and then added stuff, but I guess we can sort that out when it
>> comes to it.
> ACK.
>
> jeff
next prev parent reply other threads:[~2023-06-29 16:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 13:36 Christoph Muellner
2023-06-29 7:52 ` Christoph Müllner
2023-06-29 8:33 ` Christoph Müllner
2023-06-29 15:07 ` Jeff Law
2023-06-29 15:10 ` Christoph Müllner
2023-06-29 15:37 ` Palmer Dabbelt
2023-06-29 15:49 ` Jeff Law
2023-06-29 15:51 ` Philipp Tomsich
2023-06-30 13:40 ` Jeff Law
2023-06-30 14:06 ` Jeff Law
2023-06-30 14:08 ` Philipp Tomsich
2023-06-30 14:39 ` Jeff Law
2023-06-29 15:52 ` Palmer Dabbelt
2023-06-29 16:03 ` Jeff Law
2023-06-29 16:12 ` Palmer Dabbelt [this message]
2023-06-30 14:07 ` Philipp Tomsich
2023-06-30 0:47 ` Nelson Chu
2023-06-30 6:49 ` Kito Cheng
2023-06-30 13:38 ` Jeff Law
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-3d2267d0-e22b-4854-b92a-60a635033230@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=christoph.muellner@vrull.eu \
--cc=jbeulich@suse.com \
--cc=jeffreyalaw@gmail.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=nelson@rivosinc.com \
--cc=philipp.tomsich@vrull.eu \
--cc=research_trasio@irq.a4lg.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 read-only IMAP folder(s) and NNTP newsgroup(s).