From: Stephen Hemminger <stephen@networkplumber.org>
To: Nobuhiro MIKI <nmiki@yahoo-corp.jp>
Cc: maxime.coquelin@redhat.com, chenbo.xia@intel.com, dev@dpdk.org
Subject: Re: [PATCH 0/2] vhost: fix names to follow new naming convention
Date: Wed, 8 Mar 2023 18:40:40 -0800 [thread overview]
Message-ID: <20230308184040.2bb25613@hermes.local> (raw)
In-Reply-To: <20230309020721.22164-1-nmiki@yahoo-corp.jp>
On Thu, 9 Mar 2023 11:07:19 +0900
Nobuhiro MIKI <nmiki@yahoo-corp.jp> wrote:
> In this series, we simply replace '_slave_' with '_backend_' so that
> vhost user protocol message, protocol names follow the new naming
> conventions.
>
> Nobuhiro Miki (2):
> vhost: fix constants to follow new naming convension
> vhost: refactor to follow new naming convention
>
> drivers/vdpa/ifc/ifcvf_vdpa.c | 6 +--
> drivers/vdpa/mlx5/mlx5_vdpa.c | 4 +-
> drivers/vdpa/sfc/sfc_vdpa_ops.c | 4 +-
> lib/vhost/rte_vhost.h | 10 ++---
> lib/vhost/version.map | 2 +-
> lib/vhost/vhost.c | 4 +-
> lib/vhost/vhost.h | 4 +-
> lib/vhost/vhost_user.c | 70 ++++++++++++++++-----------------
> lib/vhost/vhost_user.h | 20 +++++-----
> 9 files changed, 62 insertions(+), 62 deletions(-)
>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
prev parent reply other threads:[~2023-03-09 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 2:07 Nobuhiro MIKI
2023-03-09 2:07 ` [PATCH 1/2] vhost: fix constants to follow new naming convension Nobuhiro MIKI
2023-03-09 3:06 ` Xia, Chenbo
2023-03-09 2:07 ` [PATCH 2/2] vhost: refactor to follow new naming convention Nobuhiro MIKI
2023-03-09 3:03 ` Xia, Chenbo
2023-03-09 4:51 ` Nobuhiro MIKI
2023-03-09 2:40 ` Stephen Hemminger [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=20230308184040.2bb25613@hermes.local \
--to=stephen@networkplumber.org \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=nmiki@yahoo-corp.jp \
/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).