DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Yong Wang <wang.yong19@zte.com.cn>, <hemant.agrawal@nxp.com>
Cc: <beilei.xing@intel.com>, <wenzhuo.lu@intel.com>,
	<john.griffin@intel.com>,  <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/4] net/dpaa: add null point check and fix mem leak
Date: Wed, 20 Dec 2017 18:28:55 +0530	[thread overview]
Message-ID: <83752162-7b5a-3567-7bc3-9ce28fec0626@nxp.com> (raw)
In-Reply-To: <1513765398-3716-1-git-send-email-wang.yong19@zte.com.cn>

On Wednesday 20 December 2017 03:53 PM, Yong Wang wrote:
> Signed-off-by: Yong Wang <wang.yong19@zte.com.cn>
> ---
>   drivers/net/dpaa/dpaa_ethdev.c | 36 +++++++++++++++++++++++++-----------
>   1 file changed, 25 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/net/dpaa/dpaa_ethdev.c b/drivers/net/dpaa/dpaa_ethdev.c
> index cf5a2ec..06d680c 100644
> --- a/drivers/net/dpaa/dpaa_ethdev.c
> +++ b/drivers/net/dpaa/dpaa_ethdev.c
> @@ -877,12 +877,17 @@ static int dpaa_debug_queue_init(struct qman_fq *fq, uint32_t fqid)
>   
Thanks for the fix!

Reviewed-By: Shreyansh Jain <shreyansh.jain@nxp.com>

  parent reply	other threads:[~2017-12-20 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 10:23 Yong Wang
2017-12-20 10:23 ` [dpdk-dev] [PATCH v2 2/4] net/i40e: " Yong Wang
2017-12-27  6:41   ` Xing, Beilei
2017-12-20 10:23 ` [dpdk-dev] [PATCH v2 3/4] net/e1000: add null point check for rte_zmalloc Yong Wang
2017-12-20 10:23 ` [dpdk-dev] [PATCH v2 4/4] crypto/qat: add null point check and fix mem leak Yong Wang
2017-12-20 12:22   ` Trahe, Fiona
2017-12-20 12:58 ` Shreyansh Jain [this message]
2018-01-17 23:00 ` [dpdk-dev] [PATCH v2 1/4] net/dpaa: " Thomas Monjalon
2018-01-22  2:53   ` [dpdk-dev] 答复: " wang.yong19
2018-01-22  7:51     ` Thomas Monjalon

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=83752162-7b5a-3567-7bc3-9ce28fec0626@nxp.com \
    --to=shreyansh.jain@nxp.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=john.griffin@intel.com \
    --cc=wang.yong19@zte.com.cn \
    --cc=wenzhuo.lu@intel.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).