From: Thomas Monjalon <thomas@monjalon.net>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 1/2] bus/fslmc: fix memory leak and cleanup
Date: Mon, 14 May 2018 00:47:36 +0200 [thread overview]
Message-ID: <2375306.ec1KVcrP50@xps> (raw)
In-Reply-To: <AM2PR04MB0753F06A227DA231E2191E2589980@AM2PR04MB0753.eurprd04.prod.outlook.com>
10/05/2018 12:46, Hemant Agrawal:
> On 5/9/2018 8:57 PM, Shreyansh Jain wrote:
> > Fixes: 828d51d8fc3e ("bus/fslmc: refactor scan and probe functions")
> > Coverity issue: 268338
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> > ---
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Series applied, thanks
prev parent reply other threads:[~2018-05-13 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 15:27 [dpdk-stable] " Shreyansh Jain
2018-05-09 15:27 ` [dpdk-stable] [PATCH 2/2] bus/fslmc: remove dead code Shreyansh Jain
2018-05-10 10:46 ` [dpdk-stable] [dpdk-dev] " Hemant Agrawal
2018-05-10 10:46 ` [dpdk-stable] [dpdk-dev] [PATCH 1/2] bus/fslmc: fix memory leak and cleanup Hemant Agrawal
2018-05-13 22:47 ` 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=2375306.ec1KVcrP50@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).