From: Thomas Monjalon <thomas@monjalon.net>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: ferruh.yigit@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: remove new to old offloads API helpers
Date: Mon, 16 Apr 2018 09:28:18 +0200 [thread overview]
Message-ID: <12699612.p0Ag6v6Uy8@xps> (raw)
In-Reply-To: <20180416060203.57358-1-shahafs@mellanox.com>
16/04/2018 08:02, Shahaf Shuler:
> According to
>
> commit 315ee8374e0e ("doc: reduce initial offload API rework scope
> to drivers")
>
> All PMDs should have moved to the new offloads API. Therefore it is safe
> to remove the new->old convert helps.
>
> The old->new helpers will remain to support application which still use
> the old API.
>
> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> ---
> lib/librte_ether/rte_ethdev.c | 100 +-----------------------------------------
> 1 file changed, 2 insertions(+), 98 deletions(-)
I think you missed removing the deprecation notice part.
next prev parent reply other threads:[~2018-04-16 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 6:02 Shahaf Shuler
2018-04-16 7:28 ` Thomas Monjalon [this message]
2018-04-17 8:33 ` [dpdk-dev] [PATCH v2] " Shahaf Shuler
2018-04-17 11:23 ` Ferruh Yigit
2018-04-17 11:53 ` Thomas Monjalon
2018-04-17 13:45 ` Ferruh Yigit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12699612.p0Ag6v6Uy8@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=shahafs@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).