All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: <dev@dpdk.org>, <santosh.shukla@caviumnetworks.com>,
	<hemant.agrawal@nxp.com>, <stable@dpdk.org>
Subject: Re: [PATCH v4 1/2] test/test: free mempool on exit
Date: Fri, 7 Apr 2017 17:42:22 +0200	[thread overview]
Message-ID: <20170407174222.7f94261c@platinum> (raw)
In-Reply-To: <1491384934-5379-1-git-send-email-shreyansh.jain@nxp.com>

On Wed, 5 Apr 2017 15:05:33 +0530, Shreyansh Jain <shreyansh.jain@nxp.com> wrote:
> mempool autotest was not freeing the mempools.
> 
> Fixes: 8ef772ae ("app/test: rework mempool tes")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> Reviewed-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>

Acked-by: Olivier Matz <olivier.matz@6wind.com>

      parent reply	other threads:[~2017-04-07 15:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 10:17 [RFC PATCH] test/test: support default mempool autotest Shreyansh Jain
2017-03-31 13:59 ` Olivier Matz
2017-03-31 14:11   ` Hemant Agrawal
2017-03-31 15:11 ` Santosh Shukla
2017-04-03  9:27   ` Hemant Agrawal
2017-04-03  9:00 ` [PATCH v2 1/2] test/test: free mempool on exit Hemant Agrawal
2017-04-03  9:00   ` [PATCH v2 2/2] test/test: support default mempool autotest Hemant Agrawal
2017-04-04  5:57   ` [PATCH v3 1/2] test/test: free mempool on exit Hemant Agrawal
2017-04-04  5:57     ` [PATCH v3 2/2] test/test: support default mempool autotest Hemant Agrawal
2017-04-05  7:02       ` santosh
2017-04-05  7:21         ` Shreyansh Jain
2017-04-04 15:28     ` [PATCH v3 1/2] test/test: free mempool on exit santosh
2017-04-05  9:35     ` [PATCH v4 " Shreyansh Jain
2017-04-05  9:35       ` [PATCH v4 2/2] test/test: support default mempool autotest Shreyansh Jain
2017-04-07 15:42         ` Olivier Matz
2017-04-19 13:10           ` Thomas Monjalon
2017-04-07 15:42       ` Olivier Matz [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=20170407174222.7f94261c@platinum \
    --to=olivier.matz@6wind.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=santosh.shukla@caviumnetworks.com \
    --cc=shreyansh.jain@nxp.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 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.