DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5 00/10] Make unit tests great again
Date: Fri, 27 Jul 2018 10:12:38 +0000	[thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A376F1C@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <9233572.sMqcLjnXGc@xps>

Hi,

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Thursday, July 26, 2018 9:05 PM
> To: Pattan, Reshma <reshma.pattan@intel.com>
> Cc: dev@dpdk.org; Burakov, Anatoly <anatoly.burakov@intel.com>;
> Parthasarathy, JananeeX M <jananeex.m.parthasarathy@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v5 00/10] Make unit tests great again
> > Reshma Pattan (10):
> >   autotest: fix printing
> >   autotest: fix invalid code on reports
> >   autotest: make autotest runner python 2/3 compliant
> >   autotest: visually separate different test categories
> >   autotest: improve filtering
> >   autotest: remove autotest grouping
> >   autotest: properly parallelize unit tests
> >   autotest: update autotest test case list
> >   mk: update make targets for classified testcases
> >   mk: remove unnecessary make rules of test
> 
> Patches 1 to 7 are from Anatoly.
> Patches 8 and 9 were initiated by Jananee.
> 
> Please fix authorship of these patches.
> Note: it should not happen if you use git-am to get the patches.
> 

Addressed in v6 and sent.

Thanks,
Reshma

      parent reply	other threads:[~2018-07-27 10:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 16:00 Reshma Pattan
2018-07-17 16:00 ` [dpdk-dev] [PATCH v5 01/10] autotest: fix printing Reshma Pattan
2018-07-17 16:00 ` [dpdk-dev] [PATCH v5 02/10] autotest: fix invalid code on reports Reshma Pattan
2018-07-17 16:00 ` [dpdk-dev] [PATCH v5 03/10] autotest: make autotest runner python 2/3 compliant Reshma Pattan
2018-07-17 16:00 ` [dpdk-dev] [PATCH v5 04/10] autotest: visually separate different test categories Reshma Pattan
2018-07-17 16:00 ` [dpdk-dev] [PATCH v5 05/10] autotest: improve filtering Reshma Pattan
2018-07-17 16:00 ` [dpdk-dev] [PATCH v5 06/10] autotest: remove autotest grouping Reshma Pattan
2018-07-17 16:00 ` [dpdk-dev] [PATCH v5 07/10] autotest: properly parallelize unit tests Reshma Pattan
2018-07-17 16:00 ` [dpdk-dev] [PATCH v5 08/10] autotest: update autotest test case list Reshma Pattan
2018-07-17 16:00 ` [dpdk-dev] [PATCH v5 09/10] mk: update make targets for classified testcases Reshma Pattan
2018-07-18  8:55   ` Burakov, Anatoly
2018-07-17 16:00 ` [dpdk-dev] [PATCH v5 10/10] mk: remove unnecessary make rules of test Reshma Pattan
2018-07-18  8:56   ` Burakov, Anatoly
2018-07-26 20:08   ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2018-07-27  8:22     ` Pattan, Reshma
2018-07-27  8:45       ` Thomas Monjalon
2018-07-26 20:04 ` [dpdk-dev] [PATCH v5 00/10] Make unit tests great again Thomas Monjalon
2018-07-27  8:36   ` Pattan, Reshma
2018-07-27  8:51     ` Burakov, Anatoly
2018-07-27 10:12   ` Pattan, Reshma [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=3AEA2BF9852C6F48A459DA490692831F2A376F1C@IRSMSX109.ger.corp.intel.com \
    --to=reshma.pattan@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jananeex.m.parthasarathy@intel.com \
    --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 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).