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 4106AA034F; Fri, 8 Oct 2021 14:54:47 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0A929410F0; Fri, 8 Oct 2021 14:54:47 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 6E9F6410EE for ; Fri, 8 Oct 2021 14:54:45 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id D4C7E5C00E7; Fri, 8 Oct 2021 08:54:43 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 08 Oct 2021 08:54:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= 3fC/sQYQNRe0T8GFwSpEUCTVdQlrkuOOeH9QUiHaUDY=; b=q5722n0HtTJ/eojd j1iQJgSujXzmq5f+3vrEegN32Ev8BBxNUPXxvnIVHiIRGr4sfttg5OBoyPUPecVP ub3RQh5N2HSovXHXW/5+GVzyethJUrmlzwcKe7gMnWkQ4ZrFsvVep6L+EuYqeZpx VkWdhjH9ywbwV6hSrZ8uX+3OXYwwDSflijhln0LqkP8kC8WgivUFj8B5YC7nGkW6 jiJfAu7LukFOci+DBc6PlLNryh1/1vLVc5MLly859xzZeP//2LHva5v/YU9LW1l7 M5uamgIGYrIUKxDfmFhQFI8o2HDMOoqsA+TtXlzxLm9wL65/MzJ5Sx5OR2HxI72l pur1BQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=3fC/sQYQNRe0T8GFwSpEUCTVdQlrkuOOeH9QUiHaU DY=; b=IWvO87G3J24KPRAha4QJjNX9LAXm77bOlcVr2vMA9sieIs2eeqfrtrqXB jfWYOkLNmVR5GW/+bFJIgKefX07LpumqbD43uYJ4+AlQ2fcqxOSrQjMaMTDQV0jc /tlfoDsjqvNmtf5swM8L7S5ICUKij497B+CE9VEM9seDjEpdr6RSpR9/txOBls9r qd/rr7uIO3xe8xmlhzeOV0+/seIQ9l//pIo9Rie0E3mqyht2aWIsDKZFWeHfMoog 7GLnPCz7o8UElZUWtNa+3rVa7kEIcK+/38LBMndhVCc1T+cpqwPD0VQ6G6M2caBm QdDu+fpmGnkuWXqRroU6JMwPwqlgA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvddttddgheeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepjeegtdffgfdugfduueeujedtgfefffegudehgedvfeegvddtjeev tdehhfekhffhnecuffhomhgrihhnpehoiihlrggsshdrohhrghenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 8 Oct 2021 08:54:42 -0400 (EDT) From: Thomas Monjalon To: Dmitry Kozlyuk Cc: dev@dpdk.org, Ferruh Yigit , Olivier Matz , Stephen Hemminger Date: Fri, 08 Oct 2021 14:54:38 +0200 Message-ID: <2511752.O9Z32RddAV@thomas> In-Reply-To: <20211007220750.313779-2-dmitry.kozliuk@gmail.com> References: <20211001163306.76538-1-dmitry.kozliuk@gmail.com> <20211007220750.313779-1-dmitry.kozliuk@gmail.com> <20211007220750.313779-2-dmitry.kozliuk@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 1/2] net: rename Ethernet header fields 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" 08/10/2021 00:07, Dmitry Kozlyuk: > --- a/doc/guides/rel_notes/deprecation.rst > +++ b/doc/guides/rel_notes/deprecation.rst > @@ -164,8 +164,13 @@ Deprecation Notices > consistent with existing outer header checksum status flag naming, which > should help in reducing confusion about its usage. > > -* net: ``s_addr`` and ``d_addr`` fields of ``rte_ether_hdr`` structure > - will be renamed in DPDK 21.11 to avoid conflict with Windows Sockets headers. > +* i40e: As there are both i40evf and iavf pmd, the functions of them are > + duplicated. And now more and more advanced features are developed on iavf. > + To keep consistent with kernel driver's name > + (https://patchwork.ozlabs.org/patch/970154/), i40evf is no need to maintain. > + Starting from 21.05, the default VF driver of i40e will be iavf, but i40evf > + can still be used if users specify the devarg "driver=i40evf". I40evf will > + be deleted in DPDK 21.11. I guess this is a rebase issue. I can fix it while merging.