From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: stable@dpdk.org, Shreyansh Jain <shreyansh.jain@nxp.com>,
olivier.matz@6wind.com, dev@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2 1/2] mempool/dpaa2: fix the return value for alloc fail
Date: Fri, 21 Jul 2017 09:29:32 +0300 [thread overview]
Message-ID: <1777391.uy2g6WzqRN@xps> (raw)
In-Reply-To: <05874f60-e427-b9e3-93da-a78e0b03d284@nxp.com>
18/07/2017 17:47, Shreyansh Jain:
> On Thursday 22 June 2017 06:18 PM, Hemant Agrawal wrote:
> > In case the alloc api is not able to allocate the required
> > number of buffer, it can return '0', which will not indicate
> > the failure to the calling function.
> > This patch fix the return value to indicate the failure.
> >
> > Fixes: 5dc43d22b5ad ("mempool/dpaa2: add hardware offloaded mempool")
> > CC: stable@dpdk.org
> >
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>
> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
Series applied, thanks
prev parent reply other threads:[~2017-07-21 6:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 9:33 [dpdk-stable] [PATCH " Hemant Agrawal
2017-05-23 9:33 ` [dpdk-stable] [PATCH 2/2] mempool/dpaa2: improving the alloc/free logging Hemant Agrawal
2017-06-08 10:08 ` Olivier Matz
2017-06-22 12:46 ` Hemant Agrawal
2017-06-08 9:53 ` [dpdk-stable] [PATCH 1/2] mempool/dpaa2: fix the return value for alloc fail Olivier Matz
2017-06-22 12:48 ` [dpdk-stable] [PATCH v2 " Hemant Agrawal
2017-06-22 12:48 ` [dpdk-stable] [PATCH v2 2/2] mempool/dpaa2: fix the incorrect free usages for bplist Hemant Agrawal
2017-07-10 8:11 ` Olivier Matz
2017-07-18 14:46 ` Shreyansh Jain
2017-07-10 8:10 ` [dpdk-stable] [PATCH v2 1/2] mempool/dpaa2: fix the return value for alloc fail Olivier Matz
2017-07-18 14:47 ` Shreyansh Jain
2017-07-21 6:29 ` 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=1777391.uy2g6WzqRN@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=olivier.matz@6wind.com \
--cc=shreyansh.jain@nxp.com \
--cc=stable@dpdk.org \
/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).