02/08/2018 11:25, Shreyansh Jain:
> On Wednesday 01 August 2018 05:37 PM, Anatoly Burakov wrote:
> > Due to the upcoming external memory support [1], some API and ABI
> > changes will be required. In addition, although the changes called
> > out in the deprecation notice are not yet present in form
On Wednesday 01 August 2018 05:37 PM, Anatoly Burakov wrote:
Due to the upcoming external memory support [1], some API and ABI
changes will be required. In addition, although the changes called
out in the deprecation notice are not yet present in form of code
in the published RFC itself, they are
On 08/01/2018 02:07 PM, Anatoly Burakov wrote:
Due to the upcoming external memory support [1], some API and ABI
changes will be required. In addition, although the changes called
out in the deprecation notice are not yet present in form of code
in the published RFC itself, they are based on c
> On Aug 1, 2018, at 5:07 AM, Anatoly Burakov wrote:
>
> Due to the upcoming external memory support [1], some API and ABI
> changes will be required. In addition, although the changes called
> out in the deprecation notice are not yet present in form of code
> in the published RFC itself, they
-Original Message-
> Date: Wed, 1 Aug 2018 13:07:16 +0100
> From: Anatoly Burakov
> To: dev@dpdk.org
> CC: Neil Horman , John McNamara
> , Marko Kovacevic ,
> tho...@monjalon.net, keith.wi...@intel.com
> Subject: [dpdk-dev] [PATCH] doc: add deprecation noti
ect: [dpdk-dev] [PATCH] doc: add deprecation notice on external
> memory support
>
> Due to the upcoming external memory support [1], some API and ABI
> changes will be required. In addition, although the changes called
> out in the deprecation notice are not yet present in form of co
> On Aug 1, 2018, at 7:07 AM, Burakov, Anatoly
> wrote:
>
> Due to the upcoming external memory support [1], some API and ABI
> changes will be required. In addition, although the changes called
> out in the deprecation notice are not yet present in form of code
> in the published RFC itself,
Due to the upcoming external memory support [1], some API and ABI
changes will be required. In addition, although the changes called
out in the deprecation notice are not yet present in form of code
in the published RFC itself, they are based on consensus on the
mailing list [2] on how to best impl
8 matches
Mail list logo
