From: Richard Henderson <richard.henderson@linaro.org>
To: Luis Pires <luis.pires@eldorado.org.br>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com
Subject: Re: [PATCH v3] docs/devel: Explain in more detail the TB chaining mechanisms
Date: Fri, 11 Jun 2021 09:45:31 -0700 [thread overview]
Message-ID: <09511b32-e56f-e448-a826-c049c70cc538@linaro.org> (raw)
In-Reply-To: <20210601125143.191165-1-luis.pires@eldorado.org.br>
On 6/1/21 5:51 AM, Luis Pires wrote:
> Signed-off-by: Luis Pires<luis.pires@eldorado.org.br>
> ---
> v3:
> - Dropped "most common" from the sentence introducing the chaining mechanisms
> - Changed wording about using the TB address returned by exit_tb
Thanks, queued.
r~
prev parent reply other threads:[~2021-06-11 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 12:51 [PATCH v3] docs/devel: Explain in more detail the TB chaining mechanisms Luis Pires
2021-06-08 18:55 ` Luis Fernando Fujita Pires
2021-06-11 16:45 ` 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=09511b32-e56f-e448-a826-c049c70cc538@linaro.org \
--to=richard.henderson@linaro.org \
--cc=luis.pires@eldorado.org.br \
--cc=pbonzini@redhat.com \
--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).