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 206FFA0A0E; Thu, 29 Apr 2021 02:49:18 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 98D44410FB; Thu, 29 Apr 2021 02:49:17 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by mails.dpdk.org (Postfix) with ESMTP id 5B73040697; Thu, 29 Apr 2021 02:49:16 +0200 (CEST) IronPort-SDR: Y9Rlnn7Io7tlqZ+XlqyZs+Ss9tWeL9lAvmnfHyJBLt3VS5vBabf0M5wlIpWUDV4U8gN14htqRM bS6GF7m1OeNg== X-IronPort-AV: E=McAfee;i="6200,9189,9968"; a="260840172" X-IronPort-AV: E=Sophos;i="5.82,258,1613462400"; d="scan'208";a="260840172" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Apr 2021 17:49:12 -0700 IronPort-SDR: QAbpeIQhnvRx+FJkGHEkVaFvv1k9hPgb0m36ynMEanxa8E34nkMdbif9KgBeL4N6RC1DxB6kx5 EJKOM8jZX3SA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.82,258,1613462400"; d="scan'208";a="458472513" Received: from fmsmsx601.amr.corp.intel.com ([10.18.126.81]) by fmsmga002.fm.intel.com with ESMTP; 28 Apr 2021 17:49:12 -0700 Received: from shsmsx605.ccr.corp.intel.com (10.109.6.215) by fmsmsx601.amr.corp.intel.com (10.18.126.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 28 Apr 2021 17:49:11 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX605.ccr.corp.intel.com (10.109.6.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 29 Apr 2021 08:49:03 +0800 Received: from shsmsx601.ccr.corp.intel.com ([10.109.6.141]) by SHSMSX601.ccr.corp.intel.com ([10.109.6.141]) with mapi id 15.01.2106.013; Thu, 29 Apr 2021 08:49:03 +0800 From: "Zhang, Qi Z" To: "Xu, Ting" , "dev@dpdk.org" CC: "Xing, Beilei" , "Wu, Jingjing" , "stable@dpdk.org" Thread-Topic: [PATCH v2] common/iavf: fix wrong order of protocol header types Thread-Index: AQHXOZ8uTvWcleHGN0yjI4SavK38/arKrzww Date: Thu, 29 Apr 2021 00:49:03 +0000 Message-ID: <3b551392ca4943fd8ef264d7b6db6ab8@intel.com> References: <20210425065304.5356-1-ting.xu@intel.com> In-Reply-To: <20210425065304.5356-1-ting.xu@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-version: 11.5.1.3 dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2] common/iavf: fix wrong order of protocol header types 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 Sender: "dev" > -----Original Message----- > From: Xu, Ting > Sent: Sunday, April 25, 2021 2:53 PM > To: dev@dpdk.org > Cc: Xing, Beilei ; Wu, Jingjing ; > Zhang, Qi Z ; Xu, Ting ; > stable@dpdk.org > Subject: [PATCH v2] common/iavf: fix wrong order of protocol header types >=20 > The new virtchnl protocol header types for IPv4 and IPv6 fragment are not > added in order, which will break ABI. Move them to the end of the list. >=20 > Signed-off-by: Ting Xu Acked-by: Qi Zhang Applied to dpdk-next-net-intel after update the base code release date in R= EADME as this is the last iavf base code update for DPDK 21.05. Thanks Qi