From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
Nipun Gupta <nipun.gupta@nxp.com>
Cc: dev@dpdk.org, Shreyansh Jain <shreyansh.jain@nxp.com>,
olivier.matz@6wind.com
Subject: Re: [dpdk-dev] [PATCH] mempool/dpaa2: alloc pool data dynamically
Date: Fri, 21 Jul 2017 09:15:53 +0300 [thread overview]
Message-ID: <1661037.diG5P5DDb3@xps> (raw)
In-Reply-To: <690813e2-1d59-5039-1ef4-1202730eddde@nxp.com>
18/07/2017 17:45, Shreyansh Jain:
> On Thursday 13 July 2017 07:48 PM, Hemant Agrawal wrote:
> > In order to support multiprocess applications, pool data is to be
> > allocated on dynamic memory instead of existing usages of global
> > variable.
> >
> > Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
>
> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
Applied, thanks
prev parent reply other threads:[~2017-07-21 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 14:18 Hemant Agrawal
2017-07-18 14:45 ` Shreyansh Jain
2017-07-21 6:15 ` 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=1661037.diG5P5DDb3@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=nipun.gupta@nxp.com \
--cc=olivier.matz@6wind.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 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).