From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Liang Ma <liang.j.ma@intel.com>
Cc: dev@dpdk.org, harry.van.haaren@intel.com,
bruce.richardson@intel.com, peter.mccarthy@intel.com
Subject: Re: [PATCH 1/2] event/opdl: fix the resource leak issue
Date: Wed, 31 Jan 2018 15:13:56 +0530 [thread overview]
Message-ID: <20180131094355.GA22413@jerin> (raw)
In-Reply-To: <1516806351-151804-1-git-send-email-liang.j.ma@intel.com>
-----Original Message-----
> Date: Wed, 24 Jan 2018 15:05:50 +0000
> From: Liang Ma <liang.j.ma@intel.com>
> To: dev@dpdk.org
> CC: harry.van.haaren@intel.com, bruce.richardson@intel.com,
> peter.mccarthy@intel.com, jerin.jacob@caviumnetworks.com
> Subject: [PATCH 1/2] event/opdl: fix the resource leak issue
> X-Mailer: git-send-email 2.7.5
>
> Fixes: d548ef513cd7 ("event/opdl: add unit tests")
> Coverity issue: 257004
>
> Signed-off-by: Liang Ma <liang.j.ma@intel.com>
Applied this series to dpdk-next-eventdev/master. Thanks.
prev parent reply other threads:[~2018-01-31 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 15:05 [PATCH 1/2] event/opdl: fix the resource leak issue Liang Ma
2018-01-24 15:05 ` [PATCH 2/2] event/opdl: fix dereference before null check Liang Ma
2018-01-31 9:43 ` Jerin Jacob [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=20180131094355.GA22413@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=liang.j.ma@intel.com \
--cc=peter.mccarthy@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 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.