From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Shahaf Shuler <shahafs@mellanox.com>,
Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: reduce initial offload API scope to drivers
Date: Sun, 15 Apr 2018 15:14:16 +0200 [thread overview]
Message-ID: <8282259.aId8a7Na6Y@xps> (raw)
In-Reply-To: <DB7PR05MB4426BD9585B35E4F6F32DA2CC3B10@DB7PR05MB4426.eurprd05.prod.outlook.com>
15/04/2018 07:28, Shahaf Shuler:
> Saturday, April 14, 2018 12:21 AM, Ferruh Yigit:
> > Subject: [PATCH v2] doc: reduce initial offload API scope to drivers
> >
> > Do ethdev new offloading API switch in two steps.
> >
> > In v18.05 target is implementing the new ethdev-PMD offload interface,
> > which means converting all PMDs to new offloading API.
> >
> > Next target is removing the old ethdev offload API.
> > It will effect applications and will force them to implement new offloading
> > API.
> >
> > Fixes: 3004d3454192 ("doc: update deprecation of ethdev offload API")
> > Cc: shahafs@mellanox.com
> >
> > Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> > ---
> > v2:
> > * Update commit log and deprecation notice for clarification
> > ---
>
> Acked-by: Shahaf Shuler <shahafs@mellanox.com>
Applied, thanks
prev parent reply other threads:[~2018-04-15 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 14:24 [dpdk-dev] [PATCH] doc: update deprecation of ethdev offload API Shahaf Shuler
2017-10-25 10:49 ` Shahaf Shuler
2017-11-08 11:16 ` Andrew Rybchenko
2017-11-10 16:41 ` Ananyev, Konstantin
2017-11-12 4:19 ` Thomas Monjalon
2018-03-16 15:31 ` [dpdk-dev] [PATCH] doc: reduce initial offload API scope to drivers Ferruh Yigit
2018-03-18 5:57 ` Shahaf Shuler
2018-03-20 14:02 ` Ferruh Yigit
2018-04-13 21:20 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-04-15 5:28 ` Shahaf Shuler
2018-04-15 13:14 ` Thomas Monjalon [this message]
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=8282259.aId8a7Na6Y@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.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).