Re: [dpdk-dev] [PATCH] doc: announce deprecation of dpaa2 exposed mem structure

2018-11-24 Thread Thomas Monjalon
23/11/2018 17:34, Jerin Jacob: > From: "Burakov, Anatoly" > > On 15-Nov-18 1:29 PM, Shreyansh Jain wrote: > > > rte_dpaa2_memsegs is no more required once the dpaax (pa-va) translation > > > library has been introduced. This can be made internal (for fallback > > > operations) in subsequent releas

Re: [dpdk-dev] [PATCH] doc: announce deprecation of dpaa2 exposed mem structure

2018-11-23 Thread Jerin Jacob
-Original Message- > Date: Fri, 23 Nov 2018 12:46:42 + > From: "Burakov, Anatoly" > To: Shreyansh Jain , "dev@dpdk.org" > Subject: Re: [dpdk-dev] [PATCH] doc: announce deprecation of dpaa2 exposed > mem structure > User-Agent: Mozilla/5.0 (

Re: [dpdk-dev] [PATCH] doc: announce deprecation of dpaa2 exposed mem structure

2018-11-23 Thread Maxime Coquelin
On 11/15/18 2:29 PM, Shreyansh Jain wrote: rte_dpaa2_memsegs is no more required once the dpaax (pa-va) translation library has been introduced. This can be made internal (for fallback operations) in subsequent release. Signed-off-by: Shreyansh Jain --- This diff was generated over a previ

Re: [dpdk-dev] [PATCH] doc: announce deprecation of dpaa2 exposed mem structure

2018-11-23 Thread Burakov, Anatoly
On 15-Nov-18 1:29 PM, Shreyansh Jain wrote: rte_dpaa2_memsegs is no more required once the dpaax (pa-va) translation library has been introduced. This can be made internal (for fallback operations) in subsequent release. Signed-off-by: Shreyansh Jain --- This diff was generated over a previou

Re: [dpdk-dev] [PATCH] doc: announce deprecation of dpaa2 exposed mem structure

2018-11-21 Thread Hemant Agrawal
Acked-by: Hemant Agrawal

[dpdk-dev] [PATCH] doc: announce deprecation of dpaa2 exposed mem structure

2018-11-15 Thread Shreyansh Jain
rte_dpaa2_memsegs is no more required once the dpaax (pa-va) translation library has been introduced. This can be made internal (for fallback operations) in subsequent release. Signed-off-by: Shreyansh Jain --- This diff was generated over a previous patch on same file (a para before) [1] - so,