From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by dpdk.space (Postfix) with ESMTP id 0B577A00E6
	for <public@inbox.dpdk.org>; Tue, 19 Mar 2019 14:50:26 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 179D12C54;
	Tue, 19 Mar 2019 14:50:25 +0100 (CET)
Received: from mail-vs1-f66.google.com (mail-vs1-f66.google.com
 [209.85.217.66]) by dpdk.org (Postfix) with ESMTP id 8EFACA3
 for <dev@dpdk.org>; Tue, 19 Mar 2019 14:50:23 +0100 (CET)
Received: by mail-vs1-f66.google.com with SMTP id h132so11719229vsd.5
 for <dev@dpdk.org>; Tue, 19 Mar 2019 06:50:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=Z0J0xJcfdXbarAnB5mxJhjQhXvDDOcObczttICbZTL4=;
 b=ZcXGshQ5QSmw5iYdoLhOQhru0AeQCimsNFB6pDiDVwve5dB32yTPZxx3Ic0Ri3goYK
 L3hOn5uklexBzzVGaYiogqwHFn2/g+BOI1HqT4dMlCL70Ltf3jUB9UHbwWVPPkg254Vq
 iv8ANYs8MXQWfUVEENjmI2kFgJmGCSKFgBUru5jPmdnTeQxmC7QMwSHhJ4Knn5q7lfo0
 Ds4BjC2nETz45X0/NaEztRGGTd61c/e/nZybBggYTdp/NSpMynvudQV6z3GCOMAuQ3sv
 v9XsewYdWMybAeyekMbTFBY49q5pjAY/rDGOFN/RyEtmwglPKC7vltL3NQztVBB4bl7C
 8YQQ==
X-Gm-Message-State: APjAAAVcM1ViSgIEoTEEVsUYq1va+qIbVOBLNZIpGR3Fzx/Ed2Gvx2FK
 LTEt9XOdLQaCU3KNsW0yuWXOcnVd2hS/WLznaSRiYg==
X-Google-Smtp-Source: APXvYqyBoyAvL3fPmUHB6Mwbkzykko6r1URkcvn+Wl6NehPga75SziAdswKnuN8t2uln9Xajy3CJDphF28fTO4nJcx0=
X-Received: by 2002:a67:c986:: with SMTP id y6mr1339696vsk.198.1553003422965; 
 Tue, 19 Mar 2019 06:50:22 -0700 (PDT)
MIME-Version: 1.0
References: <20190318154200.28409-1-qiming.yang@intel.com>
 <20190319163658.115513-1-qiming.yang@intel.com>
 <20190319163658.115513-2-qiming.yang@intel.com>
In-Reply-To: <20190319163658.115513-2-qiming.yang@intel.com>
From: David Marchand <david.marchand@redhat.com>
Date: Tue, 19 Mar 2019 14:50:12 +0100
Message-ID:
 <CAJFAV8xwg2LDh0a_9k=jqUanao+v+WrOx0xgyN_rihoBbPZadg@mail.gmail.com>
To: Qiming Yang <qiming.yang@intel.com>, Thomas Monjalon <thomas@monjalon.net>,
 "Yigit, Ferruh" <ferruh.yigit@intel.com>,
 Andrew Rybchenko <arybchenko@solarflare.com>
Cc: dev <dev@dpdk.org>, Qi Zhang <qi.z.zhang@intel.com>
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [dpdk-dev] [PATCH v4 1/5] eal: add VXLAN-GPE macro
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>
Message-ID: <20190319135012.qlZ0-KelehdBP3m9GfvXWLBaRu4rjdum4GUfYQ3FKyY@z>

eal: in the title ? we are in ethdev.

On Tue, Mar 19, 2019 at 10:14 AM Qiming Yang <qiming.yang@intel.com> wrote:

> This patch added VXLAN-GPE macro in rte_eth_tunnel_type.
>
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
> ---
>  lib/librte_ethdev/rte_eth_ctrl.h | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/lib/librte_ethdev/rte_eth_ctrl.h
> b/lib/librte_ethdev/rte_eth_ctrl.h
> index 5ea8ae2..b341634 100644
> --- a/lib/librte_ethdev/rte_eth_ctrl.h
> +++ b/lib/librte_ethdev/rte_eth_ctrl.h
> @@ -229,6 +229,7 @@ enum rte_eth_tunnel_type {
>         RTE_TUNNEL_TYPE_NVGRE,
>         RTE_TUNNEL_TYPE_IP_IN_GRE,
>         RTE_L2_TUNNEL_TYPE_E_TAG,
> +       RTE_TUNNEL_TYPE_VXLAN_GPE,
>         RTE_TUNNEL_TYPE_MAX,
>  };
>


Comments on this patch:
- is this the normal process to get an ethdev api update go through
dpdk-next-net-intel without an ethdev maintainer acking?
- does this patch introduce an api/abi breakage? (validate-abi.sh did not
complain, to my surprise)


-- 
David Marchand