From: Thomas Monjalon <thomas@monjalon.net>
To: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com, shreyansh.jain@nxp.com,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] test/test_mbuf: remove mempool global var
Date: Mon, 19 Jun 2017 22:37:09 +0200 [thread overview]
Message-ID: <2170817.cQF1WCe9mM@xps> (raw)
In-Reply-To: <20170608142831.28166-1-santosh.shukla@caviumnetworks.com>
08/06/2017 16:28, Santosh Shukla:
> Let test_mbuf alloc and free mempool.
>
> Cc: stable@dpdk.org
> Signed-off-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Why Cc stable?
Is it fixing something?
next prev parent reply other threads:[~2017-06-19 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 14:28 Santosh Shukla
2017-06-16 14:35 ` Olivier Matz
2017-06-19 20:37 ` Thomas Monjalon [this message]
2017-06-20 4:14 ` santosh
2017-06-20 7:35 ` Thomas Monjalon
2017-06-20 8:22 ` Yuanhan Liu
2017-06-22 5:31 ` santosh
2017-06-22 5:29 ` santosh
2017-06-26 10:04 ` [dpdk-dev] [PATCH v3] " Santosh Shukla
2017-06-27 17:09 ` 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=2170817.cQF1WCe9mM@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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 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).