public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: YunQiang Su <yunqiang.su@cipunited.com>
Cc: binutils@sourceware.org, syq@debian.org, xry111@xry111.site,
	 richard.sandiford@arm.com, jiaxun.yang@flygoat.com
Subject: Re: [PATCH v2 2/2] MIPS: sync oprand char usage between mips and micromips
Date: Thu, 15 Jun 2023 04:49:47 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2306150156310.64925@angie.orcam.me.uk> (raw)
In-Reply-To: <20230426101640.264902-2-yunqiang.su@cipunited.com>

On Wed, 26 Apr 2023, YunQiang Su wrote:

> We should try our best to make mips32 using the same
> oprand char with micromips. So for mips32, we use:

 I have now reverted this change, as it was committed unapproved.  If you 
want this patch in, then please repost it, get reviewed *and* approved, 
and only then you can commit it.  Thank you.

  Maciej

      reply	other threads:[~2023-06-15  3:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25  6:56 [PATCH] MIPS: add MT ASE support for micromips32 YunQiang Su
2023-04-25 10:02 ` Maciej W. Rozycki
2023-04-25 10:20   ` YunQiang Su
2023-04-25 10:25     ` YunQiang Su
2023-04-25 10:45     ` Maciej W. Rozycki
2023-05-16  6:32   ` YunQiang Su
2023-05-31  8:15     ` YunQiang Su
2023-05-31 10:28       ` Maciej W. Rozycki
2023-06-15  3:50         ` Maciej W. Rozycki
2023-04-26 10:16 ` [PATCH v2 1/2] " YunQiang Su
2023-04-26 10:16   ` [PATCH v2 2/2] MIPS: sync oprand char usage between mips and micromips YunQiang Su
2023-06-15  3:49     ` Maciej W. Rozycki [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=alpine.DEB.2.21.2306150156310.64925@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=binutils@sourceware.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=richard.sandiford@arm.com \
    --cc=syq@debian.org \
    --cc=xry111@xry111.site \
    --cc=yunqiang.su@cipunited.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).