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 B30BD41B8F; Tue, 31 Jan 2023 15:45:55 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9B46541138; Tue, 31 Jan 2023 15:45:55 +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 7A8DB40041 for ; Tue, 31 Jan 2023 15:45:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675176354; 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=MBE57Q6UQTB0aPcWk1o1ZbCaa+JsR2nVAlC7+vdGBJ4=; b=ehKuu6/gElUDZ4klcFiMzbsDDTmtoafa53FPteX3E2RX86i7ffbYAFVz23BjuniZMGpoOW BLOfNNQ8YSQOAebp8DTNjL9Zp8VvRnzThrVJ/mjy7H0dK9gYOjvZC+cC4d4aY30IDlaaWU NtCS6dq56XKsCR8WUx1baU1TdV6dHvs= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-554-NsjXh1NuMwiFVqCjK6U8nQ-1; Tue, 31 Jan 2023 09:45:50 -0500 X-MC-Unique: NsjXh1NuMwiFVqCjK6U8nQ-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5C8C0281DE6D; Tue, 31 Jan 2023 14:45:50 +0000 (UTC) Received: from [10.39.208.22] (unknown [10.39.208.22]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9EE0E112132C; Tue, 31 Jan 2023 14:45:49 +0000 (UTC) Message-ID: <45e8c686-a146-04ce-00e8-11359b9ea80b@redhat.com> Date: Tue, 31 Jan 2023 15:45:48 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: Re: [PATCH v1 3/6] baseband/acc: adding prefix to VRB1 registers To: Nicolas Chautru , dev@dpdk.org Cc: hernan.vargas@intel.com References: <20230117223642.17618-1-nicolas.chautru@intel.com> <20230117223642.17618-4-nicolas.chautru@intel.com> From: Maxime Coquelin In-Reply-To: <20230117223642.17618-4-nicolas.chautru@intel.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 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 1/17/23 23:36, Nicolas Chautru wrote: > Adding prefix to register names specific to VRB1 (ACC200) > to avoid future enum collision. > > Signed-off-by: Nicolas Chautru > --- > drivers/baseband/acc/acc200_pf_enum.h | 174 +++++++++++++------------- > drivers/baseband/acc/acc200_vf_enum.h | 128 +++++++++---------- > drivers/baseband/acc/rte_vrb_pmd.c | 136 ++++++++++---------- > drivers/baseband/acc/vrb_pmd.h | 134 ++++++++++---------- > 4 files changed, 285 insertions(+), 287 deletions(-) > Reviewed-by: Maxime Coquelin Thanks, Maxime