DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nobuhiro MIKI <nmiki@yahoo-corp.jp>, chenbo.xia@intel.com
Cc: dev@dpdk.org, stephen@networkplumber.org
Subject: Re: [PATCH v2 0/2] vhost: fix names to follow new naming convention
Date: Thu, 16 Mar 2023 15:47:59 +0100	[thread overview]
Message-ID: <389bfd03-f6f4-30b1-1dd0-54276843ec5c@redhat.com> (raw)
In-Reply-To: <20230309051643.70171-1-nmiki@yahoo-corp.jp>



On 3/9/23 06:16, Nobuhiro MIKI wrote:
> In this series, we simply replace 'master' with 'frontend' and
> 'slave' with 'backend' so that vhost user protocol message,
> protocol names follow the new naming conventions.
> 
> v2:
> - Update .mailmap in patch 1
> - Replace 'master' with 'frontend' in patch 2
> 
> Nobuhiro MIKI (2):
>    vhost: fix constants to follow new naming convention
>    vhost: refactor to follow new naming convention
> 
>   .mailmap                        |  2 +-
>   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           | 16 +++---
>   lib/vhost/version.map           |  2 +-
>   lib/vhost/vhost.c               |  4 +-
>   lib/vhost/vhost.h               |  4 +-
>   lib/vhost/vhost_crypto.c        |  2 +-
>   lib/vhost/vhost_user.c          | 90 ++++++++++++++++-----------------
>   lib/vhost/vhost_user.h          | 22 ++++----
>   11 files changed, 78 insertions(+), 78 deletions(-)
> 

Applied to dpdk-next-virtio/main.

Thanks,
Maxime


      parent reply	other threads:[~2023-03-16 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09  5:16 Nobuhiro MIKI
2023-03-09  5:16 ` [PATCH v2 1/2] vhost: fix constants " Nobuhiro MIKI
2023-03-09  5:36   ` Xia, Chenbo
2023-03-09 16:33   ` Maxime Coquelin
2023-03-09  5:16 ` [PATCH v2 2/2] vhost: refactor " Nobuhiro MIKI
2023-03-09  5:36   ` Xia, Chenbo
2023-03-09 16:33   ` Maxime Coquelin
2023-03-16 14:47 ` Maxime Coquelin [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=389bfd03-f6f4-30b1-1dd0-54276843ec5c@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=nmiki@yahoo-corp.jp \
    --cc=stephen@networkplumber.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).