DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 1/2] event/sw: add self tests to fast tests
Date: Tue, 3 Oct 2023 08:26:16 +0000	[thread overview]
Message-ID: <PH8PR11MB68034CB99188515EB1A04AB6D7C4A@PH8PR11MB6803.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1PRabmhhW2=-oC96pfw7Eq1fmkuS=JbsPBDBCxJTvYOqw@mail.gmail.com>

> -----Original Message-----
> From: Jerin Jacob <jerinjacobk@gmail.com>
> Sent: Tuesday, October 3, 2023 7:23 AM
> To: Richardson, Bruce <bruce.richardson@intel.com>; Van Haaren, Harry
> <harry.van.haaren@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [PATCH 1/2] event/sw: add self tests to fast tests
> 
> On Thu, Sep 28, 2023 at 9:01 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > By reducing the iterations for the final stage of the self-test, the SW
> > eventdev tests can be fast enough for consideration in the fast-tests
> > suite. This enables them to be run as part of the regular patch CI
> > tests, and therefore increases the chances of catching any errors in
> > patches that may affect this component.
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> 
> Looks like  --to-cmd ./scripts/get_maintainer.pl not used in sending patches.
> @Van Haaren, Harry  Could you review and Ack it to merge?

Thanks for the loop-in Jerin,

Acked-by: Harry van Haaren <harry.van.haaren@intel.com>

  reply	other threads:[~2023-10-03  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 15:14 [PATCH 0/2] Add eventdev tests to test suites Bruce Richardson
2023-09-28 15:14 ` [PATCH 1/2] event/sw: add self tests to fast tests Bruce Richardson
2023-10-03  6:23   ` Jerin Jacob
2023-10-03  8:26     ` Van Haaren, Harry [this message]
2023-09-28 15:14 ` [PATCH 2/2] event/*: add driver selftests to driver-tests suite Bruce Richardson
2023-09-29 14:22 ` [PATCH 0/2] Add eventdev tests to test suites David Marchand
2023-10-03 10:02   ` Jerin Jacob

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=PH8PR11MB68034CB99188515EB1A04AB6D7C4A@PH8PR11MB6803.namprd11.prod.outlook.com \
    --to=harry.van.haaren@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinjacobk@gmail.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).