From: Richard Henderson <rth@twiddle.net>
To: Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] s390x: Add some documentation in opcode list
Date: Mon, 11 May 2015 20:37:31 -0700 [thread overview]
Message-ID: <5551757B.7070301@twiddle.net> (raw)
In-Reply-To: <1431047528-81504-1-git-send-email-agraf@suse.de>
On 05/07/2015 06:12 PM, Alexander Graf wrote:
> I find it really hard to grasp what each field in the opcode list means.
> Slowly walking through its semantics myself, I figured I'd write a small
> summary at the top of the file to make life easier for me and whoever
> looks at the file next.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
> target-s390x/insn-data.def | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
Reviewed-by: Richard Henderson <rth@twiddle.net>
r~
prev parent reply other threads:[~2015-05-12 3:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 1:12 [Qemu-devel] [PATCH 1/2] s390x: Add some documentation in opcode list Alexander Graf
2015-05-08 1:12 ` [Qemu-devel] [PATCH 2/2] s390x: Add laa and laag instructions Alexander Graf
2015-05-12 3:53 ` Richard Henderson
2015-05-12 19:22 ` Alexander Graf
2015-05-12 3:37 ` Richard Henderson [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=5551757B.7070301@twiddle.net \
--to=rth@twiddle.net \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).