From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id E89A641E1C; Thu, 9 Mar 2023 17:33:21 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D250340ED7; Thu, 9 Mar 2023 17:33:21 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id B5AD140695 for ; Thu, 9 Mar 2023 17:33:19 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678379599; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=db4gDEZ72ZahO6IceesZ//zL1cTj5S7vN+pcUJXT4JA=; b=bujOBku2UHhkwTTnZfzzM5Jz0/rMlknjlDx4ZkQDVOGysXVZqZW8jxXnrZ4bAbe97UCv44 UrwCem5ZQvXIJ3RE3n/X2PrgeO1Ibj/CQrBtktmgxTZSw2UpRJ85eQkNm0hH2yPUBoyYUf g+DKTImg/8NKjz8QflgDNaS1erWLAKw= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-86-_oxbyxpwNuuPLYUgOF1U2A-1; Thu, 09 Mar 2023 11:33:17 -0500 X-MC-Unique: _oxbyxpwNuuPLYUgOF1U2A-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id C14B8101AA63; Thu, 9 Mar 2023 16:33:16 +0000 (UTC) Received: from [10.39.208.18] (unknown [10.39.208.18]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E8BFB35453; Thu, 9 Mar 2023 16:33:15 +0000 (UTC) Message-ID: Date: Thu, 9 Mar 2023 17:33:14 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v2 1/2] vhost: fix constants to follow new naming convention To: Nobuhiro MIKI , chenbo.xia@intel.com Cc: dev@dpdk.org, stephen@networkplumber.org References: <20230309051643.70171-1-nmiki@yahoo-corp.jp> <20230309051643.70171-2-nmiki@yahoo-corp.jp> From: Maxime Coquelin In-Reply-To: <20230309051643.70171-2-nmiki@yahoo-corp.jp> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On 3/9/23 06:16, Nobuhiro MIKI wrote: > DPDK apps (e.g. dpdk-skeleton) output this name > during negotiation. But, it is not consistent when > debugging using QEMU as a front-end, for example. > This is because QEMU already follows new naming convention [1]. > > Some type names and variable names, such as VhostUserSlaveRequest, > are still in old naming convention. But, in this patch we > only focus on constants. > > [1] https://qemu-project.gitlab.io/qemu/interop/vhost-user.html > > Signed-off-by: Nobuhiro MIKI > Acked-by: Stephen Hemminger > --- > .mailmap | 2 +- > drivers/vdpa/ifc/ifcvf_vdpa.c | 4 ++-- > drivers/vdpa/mlx5/mlx5_vdpa.c | 4 ++-- > drivers/vdpa/sfc/sfc_vdpa_ops.c | 4 ++-- > lib/vhost/rte_vhost.h | 8 ++++---- > lib/vhost/vhost_user.c | 14 +++++++------- > lib/vhost/vhost_user.h | 14 +++++++------- > 7 files changed, 25 insertions(+), 25 deletions(-) > Reviewed-by: Maxime Coquelin Thanks, Maxime