From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Shreyansh Jain <shreyansh.jain@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: announce deprecation of dpaa2 exposed mem structure
Date: Fri, 23 Nov 2018 16:34:19 +0000 [thread overview]
Message-ID: <20181123163407.GC11828@jerin> (raw)
In-Reply-To: <bf226eb5-cfab-a5f4-a336-5426eba20272@intel.com>
-----Original Message-----
> Date: Fri, 23 Nov 2018 12:46:42 +0000
> From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
> To: Shreyansh Jain <shreyansh.jain@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
> Subject: Re: [dpdk-dev] [PATCH] doc: announce deprecation of dpaa2 exposed
> mem structure
> User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
> Thunderbird/52.9.1
>
> External Email
>
> 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 <shreyansh.jain@nxp.com>
> > ---
> > This diff was generated over a previous patch on same file (a para
> > before) [1] - so, it might not apply in case [1] is missed.
> > It is possible to merge this and [1] as well, if that makes better sense.
> >
> > [1] http://patches.dpdk.org/patch/48118/
> >
> > doc/guides/rel_notes/deprecation.rst | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
>
> FWIW
>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
next prev parent reply other threads:[~2018-11-23 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 13:29 Shreyansh Jain
2018-11-21 8:50 ` Hemant Agrawal
2018-11-23 12:46 ` Burakov, Anatoly
2018-11-23 16:34 ` Jerin Jacob [this message]
2018-11-24 17:25 ` Thomas Monjalon
2018-11-23 13:51 ` Maxime Coquelin
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=20181123163407.GC11828@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=shreyansh.jain@nxp.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).