From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH v3] docs/devel/loads-stores.rst: Document our various load and store APIs
Date: Thu, 12 Oct 2017 08:10:15 -0700 [thread overview]
Message-ID: <d56cf809-5f37-2fff-bcb1-80296cf5f33a@linaro.org> (raw)
In-Reply-To: <1507655662-28101-1-git-send-email-peter.maydell@linaro.org>
On 10/10/2017 10:14 AM, Peter Maydell wrote:
> QEMU has a wide selection of different functions for doing
> loads and stores; provide some overview documentation of
> what they do and how to pick which one to use.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> Changes v2->v3: fixed the typos noticed by Eric;
> dropped the note about license in favour of using the
> default gpl2+. I think this is ready to commit now.
>
> Changes v1->v2: filled in most of the gaps thanks to the
> comments on v1.
>
> I have left some TODO markers in where they represent
> fixes we should ideally make to the API. Since this
> is for-developers internals documentation I think it's
> OK to leave those in.
>
> docs/devel/loads-stores.rst | 398 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 398 insertions(+)
> create mode 100644 docs/devel/loads-stores.rst
Modulo the 2 typos that Eric found,
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
What path should this patch take in?
r~
next prev parent reply other threads:[~2017-10-12 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 17:14 [Qemu-devel] [PATCH v3] docs/devel/loads-stores.rst: Document our various load and store APIs Peter Maydell
2017-10-10 18:38 ` Eric Blake
2017-10-12 15:10 ` Richard Henderson [this message]
2017-10-12 15:13 ` Paolo Bonzini
2017-10-12 15:23 ` Eric Blake
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=d56cf809-5f37-2fff-bcb1-80296cf5f33a@linaro.org \
--to=richard.henderson@linaro.org \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).