From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Gao Feng <gfree.wind@vip.163.com>, dev@dpdk.org
Cc: stable@dpdk.org, Gao Feng <davidfgao@tencent.com>
Subject: Re: [dpdk-stable] [PATCH v2] eal: fix unlock in rte_eal_memzone_init
Date: Fri, 7 Dec 2018 08:57:37 +0000 [thread overview]
Message-ID: <cc990e76-c705-dd1d-168c-0d64275f18f5@intel.com> (raw)
In-Reply-To: <1544145608-828-1-git-send-email-gfree.wind@vip.163.com>
On 07-Dec-18 1:20 AM, Gao Feng wrote:
> The RTE_PROC_PRIMARY error handler lost the unlock statement in the
> current codes. Now unlock and return in one place to fix it.
>
> Fixes: 49df3db84883 ("memzone: replace memzone array with fbarray")
> Cc: stable@dpdk.org
>
> Signed-off-by: Gao Feng <davidfgao@tencent.com>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-12-07 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1544057251-17351-1-git-send-email-gfree.wind@vip.163.com>
2018-12-07 1:20 ` Gao Feng
2018-12-07 8:57 ` Burakov, Anatoly [this message]
2018-12-20 11:20 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2018-12-20 11:44 ` Gao Feng
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=cc990e76-c705-dd1d-168c-0d64275f18f5@intel.com \
--to=anatoly.burakov@intel.com \
--cc=davidfgao@tencent.com \
--cc=dev@dpdk.org \
--cc=gfree.wind@vip.163.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).