From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Renata Saiakhova <Renata.Saiakhova@ekinops.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 1/4] librte_ethdev: Introduce a function to release HW rings
Date: Thu, 14 May 2020 14:14:18 +0100 [thread overview]
Message-ID: <faeac643-3ea4-7e4e-a3f5-d4356b3af8fa@intel.com> (raw)
In-Reply-To: <20200513131425.27817-2-Renata.Saiakhova@ekinops.com>
On 13-May-20 2:14 PM, Renata Saiakhova wrote:
> Free previously allocated memzone for HW rings
>
> Signed-off-by: Renata Saiakhova <Renata.Saiakhova@ekinops.com>
> ---
Unless significant changes to the patch was made, you can keep the ack
from the previous version. In the future, please add it to the commit
message.
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2020-05-14 13:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 13:14 [dpdk-dev] [PATCH v3 0/4] Memory corruption due to HW rings allocation Renata Saiakhova
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 1/4] librte_ethdev: Introduce a function to release HW rings Renata Saiakhova
2020-05-14 13:14 ` Burakov, Anatoly [this message]
2020-05-15 8:04 ` Jeff Guo
2020-06-19 17:06 ` Ferruh Yigit
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 2/4] drivers/net: Fix in igb and ixgbe HW rings memory Renata Saiakhova
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 3/4] drivers/net: Fix in i40e HW rings memory overlap Renata Saiakhova
2020-06-01 7:58 ` Zhao1, Wei
2020-06-19 16:56 ` Ferruh Yigit
2020-06-20 3:02 ` Zhao1, Wei
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 4/4] drivers/net: Fix in em and ice " Renata Saiakhova
2020-05-13 15:22 ` [dpdk-dev] [PATCH v3 0/4] Memory corruption due to HW rings allocation Ferruh Yigit
2020-05-18 9:48 ` Renata Saiakhova
2020-06-03 1:36 ` Zhao1, Wei
2020-06-19 16:54 ` Ferruh Yigit
2020-06-19 16:54 ` Ferruh Yigit
2020-06-22 9:59 ` Renata Saiakhova
2020-06-20 3:27 ` Zhao1, Wei
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=faeac643-3ea4-7e4e-a3f5-d4356b3af8fa@intel.com \
--to=anatoly.burakov@intel.com \
--cc=Renata.Saiakhova@ekinops.com \
--cc=dev@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).