From: Nick Clifton <nickc@redhat.com>
To: Jens Remus <jremus@linux.ibm.com>, binutils@sourceware.org
Cc: Andreas Krebbel <krebbel@linux.ibm.com>
Subject: Re: [PATCH v2 4/6] s390: Align optional operand definition to specs
Date: Thu, 23 Nov 2023 11:58:59 +0000 [thread overview]
Message-ID: <5ec258dc-272f-446a-97ce-b552bcd683ed@redhat.com> (raw)
In-Reply-To: <20231122160643.1326583-1-jremus@linux.ibm.com>
Hi Jens,
> opcodes/
> * s390-opc.txt: Align optional operand definition to
> specification.
>
> testsuite/
> * zarch-z10.s: Add test cases for risbg, risbgz, rnsbg, rosbg,
> and rxsbg.
> * zarch-z10.d: Likewise.
> * zarch-z196.s: Add test cases for risbhg and risblg.
> * zarch-z196.d: Likewise.
> * zarch-zEC12.s: Add test cases for risbgn and risbgnz.
> * zarch-zEC12.d: Likewise.
>
> Signed-off-by: Jens Remus <jremus@linux.ibm.com>
> Reviewed-by: Andreas Krebbel <krebbel@linux.ibm.com>
Approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2023-11-23 11:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 14:06 [PATCH 0/6] s390: Add missing extended mnemonics Jens Remus
2023-11-20 14:06 ` [PATCH 1/6] s390: Position independent verification of relative addressing Jens Remus
2023-11-20 14:06 ` [PATCH 2/6] s390: Add brasl edge test cases from ESA to z/Architecture Jens Remus
2023-11-20 14:06 ` [PATCH 3/6] s390: Make operand table indices relative to each other Jens Remus
2023-11-20 14:06 ` [PATCH 4/6] s390: Align optional operand definition to specs Jens Remus
2023-11-22 16:06 ` [PATCH v2 " Jens Remus
2023-11-23 11:58 ` Nick Clifton [this message]
2023-11-20 14:06 ` [PATCH 5/6] s390: Add missing extended mnemonics Jens Remus
2023-11-22 16:07 ` [PATCH v2 " Jens Remus
2023-11-23 11:59 ` Nick Clifton
2023-11-20 14:06 ` [PATCH 6/6] s390: Correct prno instruction name Jens Remus
2023-11-22 12:13 ` [PATCH 0/6] s390: Add missing extended mnemonics Nick Clifton
2023-11-22 16:25 ` Jens Remus
2023-11-23 14:53 ` Andreas Krebbel
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=5ec258dc-272f-446a-97ce-b552bcd683ed@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=jremus@linux.ibm.com \
--cc=krebbel@linux.ibm.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).