From: David Marchand <david.marchand@redhat.com>
To: Lavanya Govindarajan <lavanyax.govindarajan@intel.com>
Cc: dev <dev@dpdk.org>, "Pattan, Reshma" <reshma.pattan@intel.com>,
Olivier Matz <olivier.matz@6wind.com>,
Bruce Richardson <bruce.richardson@intel.com>,
"Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>,
Pallantla Poornima <pallantlax.poornima@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5 0/2] add unit test cases for mbuf library
Date: Thu, 24 Oct 2019 09:54:49 +0200 [thread overview]
Message-ID: <CAJFAV8zzcOn8Y9UQVMuSzGGe-Mvi=qpS2cYwqZneCTpBrB-OnQ@mail.gmail.com> (raw)
In-Reply-To: <1567174395-27432-1-git-send-email-lavanyax.govindarajan@intel.com>
On Fri, Aug 30, 2019 at 4:14 PM Lavanya Govindarajan
<lavanyax.govindarajan@intel.com> wrote:
>
> This patchset contains unit testcases added to increase the
> functional and decision coverage for the library functions
> defined in rte_mbuf.h and rte_mbuf.c
>
> 1/2: unit test cases added for rte_mbuf.h
> 2/2: unit test cases added for rte_mbuf.c
>
> Patch 2/2 depends on 1/2
>
> Signed-off-by: Lavanya Govindarajan <lavanyax.govindarajan@intel.com>
> Signed-off-by: Pallantla Poornima <pallantlax.poornima@intel.com>
> Reviewed-by: Reshma Pattan <reshma.pattan@intel.com>
> Acked-by: Olivier Matz <olivier.matz@6wind.com>
Applied, thanks.
--
David Marchand
next prev parent reply other threads:[~2019-10-24 7:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 12:40 [dpdk-dev] [PATCH] app/test: add unit test cases for mbuf library APIs Lavanya Govindarajan
2019-04-15 12:40 ` Lavanya Govindarajan
2019-05-31 10:45 ` Pattan, Reshma
2019-06-03 8:39 ` Olivier Matz
2019-07-22 13:32 ` Govindarajan, LavanyaX
2019-08-13 10:26 ` Govindarajan, LavanyaX
2019-08-22 11:21 ` Govindarajan, LavanyaX
2019-07-22 13:42 ` [dpdk-dev] [PATCH v2 0/2] add unit test cases for mbuf library Lavanya Govindarajan
2019-07-22 13:42 ` [dpdk-dev] [PATCH v2 1/2] app/test: add unit test cases for mbuf library APIs Lavanya Govindarajan
2019-07-22 13:42 ` [dpdk-dev] [PATCH v2 2/2] app/test: add unit test cases to mbuf Lavanya Govindarajan
2019-07-23 12:14 ` [dpdk-dev] [PATCH v3 0/2] add unit test cases for mbuf library Lavanya Govindarajan
2019-07-23 12:14 ` [dpdk-dev] [PATCH v3 1/2] app/test: add unit test cases for mbuf library APIs Lavanya Govindarajan
2019-08-08 13:34 ` [dpdk-dev] [PATCH v4 0/2] add unit test cases for mbuf library Lavanya Govindarajan
2019-08-08 13:34 ` [dpdk-dev] [PATCH v4 1/2] app/test: add unit test cases for mbuf library APIs Lavanya Govindarajan
2019-08-26 8:47 ` Olivier Matz
2019-08-30 14:13 ` [dpdk-dev] [PATCH v5 0/2] add unit test cases for mbuf library Lavanya Govindarajan
2019-10-24 7:54 ` David Marchand [this message]
2019-08-30 14:13 ` [dpdk-dev] [PATCH v5 1/2] app/test: add unit test cases for mbuf library APIs Lavanya Govindarajan
2019-08-30 14:13 ` [dpdk-dev] [PATCH v5 2/2] app/test: add unit test for mbuf flag names Lavanya Govindarajan
2019-08-08 13:34 ` [dpdk-dev] [PATCH v4 2/2] app/test: add unit test cases to mbuf Lavanya Govindarajan
2019-08-26 9:09 ` Olivier Matz
2019-07-23 12:14 ` [dpdk-dev] [PATCH v3 " Lavanya Govindarajan
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='CAJFAV8zzcOn8Y9UQVMuSzGGe-Mvi=qpS2cYwqZneCTpBrB-OnQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jananeex.m.parthasarathy@intel.com \
--cc=lavanyax.govindarajan@intel.com \
--cc=olivier.matz@6wind.com \
--cc=pallantlax.poornima@intel.com \
--cc=reshma.pattan@intel.com \
/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).