From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: qemu-devel@nongnu.org, mst@redhat.com, pbonzini@redhat.com,
stephen@networkplumber.org, chenbo.xia@intel.com,
thomas@monjalon.net, dmarchan@redhat.com
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [PATCH 0/3] Vhost-user: replace _SLAVE_ with _BACKEND_
Date: Mon, 30 Jan 2023 11:45:45 +0100 [thread overview]
Message-ID: <20230130104548.13262-1-maxime.coquelin@redhat.com> (raw)
This series continues the work done to get rid of harmful
language in the Vhost-user specification.
While the spec texts were changed to replace slave with
backend, the protocol features and messages names hadn't
been changed.
This series renames remaining occurences in the spec and
make use of the new names in both libvhost-user and the
Vhost-user frontend code.
Maxime Coquelin (3):
docs: vhost-user: replace _SLAVE_ with _BACKEND_
libvhost-user: Adopt new backend naming
vhost-user: Adopt new backend naming
docs/interop/vhost-user.rst | 40 +++++++++++------------
hw/virtio/vhost-user.c | 30 ++++++++---------
hw/virtio/virtio-qmp.c | 12 +++----
subprojects/libvhost-user/libvhost-user.c | 20 ++++++------
subprojects/libvhost-user/libvhost-user.h | 20 ++++++------
5 files changed, 61 insertions(+), 61 deletions(-)
--
2.39.1
next reply other threads:[~2023-01-30 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 10:45 Maxime Coquelin [this message]
2023-01-30 10:45 ` [PATCH 1/3] docs: vhost-user: replace _SLAVE_ with _BACKEND_ Maxime Coquelin
2023-01-30 11:10 ` Michael S. Tsirkin
2023-01-30 10:45 ` [PATCH 2/3] libvhost-user: Adopt new backend naming Maxime Coquelin
2023-01-30 11:11 ` Michael S. Tsirkin
2023-01-30 10:45 ` [PATCH 3/3] vhost-user: " Maxime Coquelin
2023-01-30 11:12 ` Michael S. Tsirkin
2023-01-30 11:08 ` [PATCH 0/3] Vhost-user: replace _SLAVE_ with _BACKEND_ Michael S. Tsirkin
2023-01-30 11:48 ` Maxime Coquelin
2023-01-30 16:44 ` Stephen Hemminger via
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=20230130104548.13262-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dmarchan@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.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).