From: Andreas Krebbel <krebbel@linux.ibm.com>
To: Jens Remus <jremus@linux.ibm.com>, binutils@sourceware.org
Cc: Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH v2 0/7] s390: Optionally print instruction description in disassembly
Date: Wed, 20 Dec 2023 11:56:22 +0100 [thread overview]
Message-ID: <2462fa3b-91d9-436f-b4a6-b76f44b82cd7@linux.ibm.com> (raw)
In-Reply-To: <20231215143616.820185-1-jremus@linux.ibm.com>
> Jens Remus (7):
> s390: Fix build when using EXEEXT_FOR_BUILD
> s390: Align letter case of instruction descriptions
> s390: Provide IBM z16 (arch14) instruction descriptions
> s390: Enhance error handling in s390-mkopc
> s390: Use safe string functions and length macros in s390-mkopc
> s390: Optionally print instruction description in disassembly
> s390: Add suffix to conditional branch instruction descriptions
Committed to mainline. Thanks!
Andreas
prev parent reply other threads:[~2023-12-20 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 14:36 Jens Remus
2023-12-15 14:36 ` [PATCH v2 1/7] s390: Fix build when using EXEEXT_FOR_BUILD Jens Remus
2023-12-15 14:36 ` [PATCH v2 2/7] s390: Align letter case of instruction descriptions Jens Remus
2023-12-15 14:36 ` [PATCH v2 3/7] s390: Provide IBM z16 (arch14) " Jens Remus
2023-12-15 14:36 ` [PATCH v2 4/7] s390: Enhance error handling in s390-mkopc Jens Remus
2023-12-15 14:36 ` [PATCH v2 5/7] s390: Use safe string functions and length macros " Jens Remus
2023-12-15 14:36 ` [PATCH v2 6/7] s390: Optionally print instruction description in disassembly Jens Remus
2023-12-15 14:36 ` [PATCH v2 7/7] s390: Add suffix to conditional branch instruction descriptions Jens Remus
2023-12-18 12:14 ` [PATCH v2 0/7] s390: Optionally print instruction description in disassembly Nick Clifton
2023-12-20 10:56 ` Andreas Krebbel [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=2462fa3b-91d9-436f-b4a6-b76f44b82cd7@linux.ibm.com \
--to=krebbel@linux.ibm.com \
--cc=binutils@sourceware.org \
--cc=jremus@linux.ibm.com \
--cc=nickc@redhat.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).