From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com, jag.raman@oracle.com, stefanha@redhat.com,
sgarzare@redhat.com
Subject: [PATCH 0/3] docs: replace master/slave with more accurate wording
Date: Fri, 26 Feb 2021 09:34:10 -0500 [thread overview]
Message-ID: <20210226143413.188046-1-pbonzini@redhat.com> (raw)
Usually front-end/back-end are used for the two vhost sides rather than
master/slave. Use them in the documentation as they identify more
clearly what is going on (plus, the documentation was sometimes using
client/server instead).
Jag, would you mind doing the same for multiprocess too?
Paolo
Paolo Bonzini (3):
docs: vhost-user: clean up request/reply description
docs: vhost-user: rewrite section on ring state machine
docs: vhost-user: replace master/slave with front-end/back-end
docs/interop/vhost-user-gpu.rst | 10 +-
docs/interop/vhost-user.rst | 537 +++++++++++++++++---------------
2 files changed, 285 insertions(+), 262 deletions(-)
--
2.26.2
next reply other threads:[~2021-02-26 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 14:34 Paolo Bonzini [this message]
2021-02-26 14:34 ` [PATCH 1/3] docs: vhost-user: clean up request/reply description Paolo Bonzini
2021-03-01 8:12 ` Philippe Mathieu-Daudé
2021-03-01 10:16 ` Stefan Hajnoczi
2021-03-01 10:32 ` Stefano Garzarella
2021-03-01 10:49 ` Paolo Bonzini
2021-03-01 11:33 ` Alex Bennée
2021-02-26 14:34 ` [PATCH 2/3] docs: vhost-user: rewrite section on ring state machine Paolo Bonzini
2021-03-01 10:16 ` Stefan Hajnoczi
2021-02-26 14:34 ` [PATCH 3/3] docs: vhost-user: replace master/slave with front-end/back-end Paolo Bonzini
2021-03-01 10:23 ` Stefan Hajnoczi
2021-03-01 10:48 ` Paolo Bonzini
2021-02-26 14:48 ` [PATCH 0/3] docs: replace master/slave with more accurate wording Jag Raman
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=20210226143413.188046-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=jag.raman@oracle.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@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 NNTP newsgroup(s).