From: Jan Beulich <jbeulich@suse.com>
To: Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Nelson Chu <nelson@rivosinc.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 0/2] RISC-V: a little more macro insn handling adjusting
Date: Fri, 17 Nov 2023 11:18:12 +0100 [thread overview]
Message-ID: <c87cfed0-3c1f-436f-b5a3-d943ea0c93ef@suse.com> (raw)
In-Reply-To: <8255d3af-23e4-054d-be6c-28fae6a76ea0@suse.com>
On 03.11.2023 13:55, Jan Beulich wrote:
> 1: disallow x0 with certain macro-insns
> 2: reduce redundancy in sign/zero extension macro insn handling
Not hearing anything back kind of suggests no objections. I'll commit
these two patches at the end of next week unless I hear back earlier.
Jan
> See also the remark in patch 1 towards possible further tidying.
>
> Jan
next prev parent reply other threads:[~2023-11-17 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 12:55 Jan Beulich
2023-11-03 12:56 ` [PATCH 1/2] RISC-V: disallow x0 with certain macro-insns Jan Beulich
2023-11-24 8:59 ` Christoph Müllner
2023-11-24 9:10 ` Jan Beulich
2023-11-03 12:57 ` [PATCH 2/2] RISC-V: reduce redundancy in sign/zero extension macro insn handling Jan Beulich
2023-11-17 10:18 ` Jan Beulich [this message]
2023-11-22 0:26 ` [PATCH 0/2] RISC-V: a little more macro insn handling adjusting Palmer Dabbelt
2023-11-22 0:39 ` Andrew Waterman
2023-11-22 7:59 ` Jan Beulich
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=c87cfed0-3c1f-436f-b5a3-d943ea0c93ef@suse.com \
--to=jbeulich@suse.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=jim.wilson.gcc@gmail.com \
--cc=nelson@rivosinc.com \
--cc=palmer@dabbelt.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).