From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: Richard Henderson <rth@twiddle.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg: Add documentation for missing tcg-ops
Date: Sat, 10 Jan 2015 21:15:07 +0000 [thread overview]
Message-ID: <54B1965B.6020804@mail.uni-paderborn.de> (raw)
In-Reply-To: <54B17F5D.9030801@twiddle.net>
Sorry ..., I did not use reply all ...
On 01/10/2015 07:37 PM, Richard Henderson wrote:
> On 01/10/2015 08:51 AM, Bastian Koppelmann wrote:
>> The documentation for the tcg-ops subfi, extr_i64_i32 and extr32_i64 was still
>> missing.
>
> No, there are no such tcg ops.
>
> There are *functions* by these names in tcg-op.h, but no opcodes.
> If you want to document this sort of thing, it should go elsewhere.
>
>
> r~
Fair enough. Where would you recommend to put the documentation?
Cheers,
Bastian
next prev parent reply other threads:[~2015-01-10 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 16:51 [Qemu-devel] [PATCH] tcg: Add documentation for missing tcg-ops Bastian Koppelmann
2015-01-10 19:37 ` Richard Henderson
2015-01-10 21:15 ` Bastian Koppelmann [this message]
2015-01-10 20:50 ` Richard Henderson
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=54B1965B.6020804@mail.uni-paderborn.de \
--to=kbastian@mail.uni-paderborn.de \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).