From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wj0-f179.google.com (mail-wj0-f179.google.com
 [209.85.210.179]) by dpdk.org (Postfix) with ESMTP id 2F4072E83
 for <dev@dpdk.org>; Fri,  9 Dec 2016 14:04:35 +0100 (CET)
Received: by mail-wj0-f179.google.com with SMTP id tk12so14120022wjb.3
 for <dev@dpdk.org>; Fri, 09 Dec 2016 05:04:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=6wind-com.20150623.gappssmtp.com; s=20150623;
 h=from:to:cc:subject:date:message-id:user-agent:in-reply-to
 :references:mime-version:content-transfer-encoding;
 bh=zpEMoIHSw1gMuVpLFMrMY4doZczpAaP3OEvPc4jOD68=;
 b=yNRwSLzcxgzzsm2U/JBnDTsTVu/mrO/+zoRK3iIRHEBTbrACMinEwkU6Lswk34s3sf
 gkAheNIeX+1EuQaUIU+iwSLo/bXIJ4qvQxpA4iFSODB9jvju9IkskWn4XjURnTW4MmOS
 /El7VE4iyiWRFQJBNnATkXgmGPR1UpbZMlCkfdbtsD7/pk1ystfgushB+O74SzcKYL66
 Pz8xcszpc2Csg6AVET3VnJIRX18J989SYtaOsss2qrgcYtXNneBLr4M5/EsAm7NTED8C
 qaP+lRc0Wpy1JjN051Abxh0hcb0phSfRQsVJsU3eSx5/HNkQPz8KZhboO/lik3ZPOy9k
 rEfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent
 :in-reply-to:references:mime-version:content-transfer-encoding;
 bh=zpEMoIHSw1gMuVpLFMrMY4doZczpAaP3OEvPc4jOD68=;
 b=jQJQEtWcVZy5h1WmOUoSqeTkEZDpEwzU+cZySSAYBF7K69HKEgkawnfwUjjUkLK8sY
 5nrJKq9TYpB/BwOY/f7FVtBnspCokNVYEFUIaNRu8pethkOTfNi5doZ72yqSJejmm8oE
 WcpvhSdU1P3+xRRcPuWX+jGyyRXg28T+qzWji+pQVnc41B1ouEtkBHJ07GRCouOsBkib
 tRxFCGGPKUvG/gMimDyGRb/t79MklXvMOEHs0kufhfByglWy2wJ2DnH3bD7sW+L/B5C1
 05M0cenMM1uwOVatGNgud3hh0Gnsvu74xJxl4QH7eey3cU7OQ1N1Bg5BmQR+J3FQ7LjF
 DpxQ==
X-Gm-Message-State: AKaTC02s0XUKPiw0VnGBmuFB7EJV/wAP/629kZoHXjmoX+LwntCIkOmYOEuLtu+Re+Kzcx8V
X-Received: by 10.195.30.165 with SMTP id kf5mr67899630wjd.41.1481288674803;
 Fri, 09 Dec 2016 05:04:34 -0800 (PST)
Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184])
 by smtp.gmail.com with ESMTPSA id q65sm20504161wmd.6.2016.12.09.05.04.33
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Fri, 09 Dec 2016 05:04:34 -0800 (PST)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>, dev@dpdk.org
Date: Fri, 09 Dec 2016 14:04:32 +0100
Message-ID: <29626520.OD9qkZZgkn@xps13>
User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; )
In-Reply-To: <8CEF83825BEC744B83065625E567D7C224D0601D@IRSMSX108.ger.corp.intel.com>
References: <1481282878-26176-1-git-send-email-bernard.iremonger@intel.com>
 <c6b63a88-bf65-8096-5bae-5cfdff161dc2@intel.com>
 <8CEF83825BEC744B83065625E567D7C224D0601D@IRSMSX108.ger.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH v1 0/5] net/ixgbe: move set VF functions.
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2016 13:04:36 -0000

2016-12-09 12:00, Iremonger, Bernard:
> From: Yigit, Ferruh
> > Why this patchset doesn't remove ethdev updates for these functions?
> > 
> > ixgbe is the only user for these eth-dev_ops, since code moved to ixgbe
> > driver, they and relevant rte_eth_xx functions (and deprecation notice) can
> > be removed in this patchset. Most probably after testpmd updated to
> > prevent compilation errors.
> 
> My understanding is that the functions should be copied and reworked before being removed from the ethdev, and that the removal should be done in a separate patch set.
> 
> Hi Thomas,
> 
> Could you clarify please.

It was announced that these functions will be removed,
so they can be safely removed in 17.02, right?
In this case, it is a code move: copy, rework and delete in the same patch.
And yes, the deprecation notice must be removed at the same time.