All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Power, Ciara" <ciara.power@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"aconole@redhat.com" <aconole@redhat.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc/guides: add details for new test structure
Date: Fri, 26 Nov 2021 17:54:07 +0100	[thread overview]
Message-ID: <2280091.bkzKxzg5bf@thomas> (raw)
In-Reply-To: <MN2PR11MB3821720FB1BB00544C67D921E6BC9@MN2PR11MB3821.namprd11.prod.outlook.com>

> >The testing guide is now updated to include details about using sub-testsuites.
> >Some example code is given to demonstrate how they can be used.
> >
> >A note is also added to highlight the need for using vdev EAL args when
> >running cryptodev tests.
> >
> >Signed-off-by: Ciara Power <ciara.power@intel.com>
> >
> >---
> >Depends-on: patch-101811 ("guides: add a guide for developing unit tests")
> >
> 
> Adding missed acks from v2.
> 
> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
> Acked-by: John McNamara <john.mcnamara@intel.com>

Applied with few formatting changes, thanks.




      reply	other threads:[~2021-11-26 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 15:55 [dpdk-dev] [PATCH] doc/guides: add details for new test structure Ciara Power
2021-05-17 18:01 ` Aaron Conole
2021-05-18 14:30   ` Power, Ciara
2021-07-16 13:40 ` [dpdk-dev] [PATCH v2] " Ciara Power
2021-07-19 11:06   ` Zhang, Roy Fan
2021-07-31 17:41   ` Thomas Monjalon
2021-08-03 12:11     ` Power, Ciara
2021-08-06 10:00   ` Mcnamara, John
2021-10-18 14:50 ` [dpdk-dev] [PATCH v3] " Ciara Power
2021-10-18 14:54   ` Power, Ciara
2021-11-26 16:54     ` Thomas Monjalon [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=2280091.bkzKxzg5bf@thomas \
    --to=thomas@monjalon.net \
    --cc=aconole@redhat.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=roy.fan.zhang@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 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.