From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Aaron Conole <aconole@redhat.com>, dev@dpdk.org
Cc: Herakliusz Lipiec <herakliusz.lipiec@intel.com>,
stable@dpdk.org, David Marchand <dmarchan@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v2] ipc: unlock on failure
Date: Thu, 9 May 2019 12:50:55 +0100 [thread overview]
Message-ID: <1b580bd4-e2c7-d018-f7ea-6b8e7c6b342e@intel.com> (raw)
Message-ID: <20190509115055.y-y2KK4PaNW2jxBI_ZnXK7ff3vuGFLWoAk2iebZKRzo@z> (raw)
In-Reply-To: <20190506134825.20706-1-aconole@redhat.com>
On 06-May-19 2:48 PM, Aaron Conole wrote:
> Reported by Coverity.
Maybe have a more descriptive commit message?
>
> Fixes: a2a06860b8c4 ("ipc: fix memory leak on request failure")
> Cc: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
> Cc: stable@dpdk.org
> Cc: Anatoly Burakov <anatoly.burakov@intel.com>
> Signed-off-by: Aaron Conole <aconole@redhat.com>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-05-09 11:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 13:11 [dpdk-dev] [PATCH] " Aaron Conole
2019-05-06 13:11 ` Aaron Conole
2019-05-06 13:14 ` David Marchand
2019-05-06 13:14 ` David Marchand
2019-05-06 13:22 ` Aaron Conole
2019-05-06 13:22 ` Aaron Conole
2019-05-06 13:48 ` [dpdk-dev] [PATCH v2] " Aaron Conole
2019-05-06 13:48 ` Aaron Conole
2019-05-06 14:02 ` David Marchand
2019-05-06 14:02 ` David Marchand
2019-05-08 14:24 ` Stojaczyk, Dariusz
2019-05-08 14:24 ` Stojaczyk, Dariusz
2019-05-09 11:50 ` Burakov, Anatoly [this message]
2019-05-09 11:50 ` Burakov, Anatoly
2019-05-09 14:31 ` Thomas Monjalon
2019-05-09 14:31 ` 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=1b580bd4-e2c7-d018-f7ea-6b8e7c6b342e@intel.com \
--to=anatoly.burakov@intel.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=dmarchan@redhat.com \
--cc=herakliusz.lipiec@intel.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).