All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: dev@dpdk.org, Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [PATCH] doc: announce deprecation of dpaa2 exposed mem structure
Date: Sat, 24 Nov 2018 18:25:53 +0100	[thread overview]
Message-ID: <1684185.YyXtGizyeL@xps> (raw)
In-Reply-To: <20181123163407.GC11828@jerin>

23/11/2018 17:34, Jerin Jacob:
> From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
> > 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>

Applied

  reply	other threads:[~2018-11-24 17:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 13:29 [PATCH] doc: announce deprecation of dpaa2 exposed mem structure Shreyansh Jain
2018-11-21  8:50 ` Hemant Agrawal
2018-11-23 12:46 ` Burakov, Anatoly
2018-11-23 16:34   ` Jerin Jacob
2018-11-24 17:25     ` Thomas Monjalon [this message]
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=1684185.YyXtGizyeL@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.