All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 1/2] test/memzone: add test for memzone count in eal mem config
Date: Thu, 1 Feb 2018 10:05:56 +0000	[thread overview]
Message-ID: <369a211f-1ccd-c81f-1911-5417a2441a2f@intel.com> (raw)
In-Reply-To: <10403071.adUGvGvJF3@xps>

On 01-Feb-18 12:12 AM, Thomas Monjalon wrote:
> 31/01/2018 16:29, Anatoly Burakov:
>> Ensure that memzone count in eal mem config is incremented and
>> decremented whenever memzones are allocated and freed.
>>
>> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> 
> Please report acks from previous version.
> 
> 
OK, will submit a v4.

-- 
Thanks,
Anatoly

  reply	other threads:[~2018-02-01 10:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26 17:40 [PATCH 1/2] test/memzone: add test for memzone count in eal mem config Anatoly Burakov
2018-01-26 17:40 ` [PATCH 2/2] test/memzone: handle previously allocated memzones Anatoly Burakov
2018-01-27 14:46   ` Radoslaw Biernacki
2018-01-31  7:51   ` Phil Yang
2018-01-31 10:05     ` Burakov, Anatoly
2018-01-31 10:08       ` Phil Yang
2018-01-27 14:53 ` [PATCH 1/2] test/memzone: add test for memzone count in eal mem config Radoslaw Biernacki
2018-01-29  9:40   ` Burakov, Anatoly
2018-01-31 15:29 ` [PATCH v2 " Anatoly Burakov
2018-02-01  0:12   ` Thomas Monjalon
2018-02-01 10:05     ` Burakov, Anatoly [this message]
2018-02-01 10:02   ` [PATCH v3 " Anatoly Burakov
2018-02-01 10:14     ` [PATCH v4 " Anatoly Burakov
2018-02-06  0:49       ` Thomas Monjalon
2018-02-01 10:14     ` [PATCH v4 2/2] test/memzone: handle previously allocated memzones Anatoly Burakov
2018-02-01 10:02   ` [PATCH v3 " Anatoly Burakov
2018-01-31 15:29 ` [PATCH v2 " Anatoly Burakov

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=369a211f-1ccd-c81f-1911-5417a2441a2f@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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.