From: Jerin Jacob <jerinjacobk@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
dev@dpdk.org, Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH 0/2] Add eventdev tests to test suites
Date: Tue, 3 Oct 2023 15:32:47 +0530 [thread overview]
Message-ID: <CALBAE1M=ZXT-LO_VibQMaBMyAkgW10oP7w5Zk2W70pcykrzdxQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8zcQ4WjsEr-2+PcVVRfSUXid4OZ+GookJg91XrM3VZ9VQ@mail.gmail.com>
On Sat, Sep 30, 2023 at 6:31 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Thu, Sep 28, 2023 at 5:14 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > The eventdev library includes a selftest API which can be used by
> > drivers for testing. Add the relevant automated self-test commands
> > into meson test suites as appropriate.
> >
> > Bruce Richardson (2):
> > event/sw: add self tests to fast tests
> > event/*: add driver selftests to driver-tests suite
> >
> > app/test/test_eventdev.c | 10 +++++-----
> > drivers/event/sw/sw_evdev_selftest.c | 2 +-
> > 2 files changed, 6 insertions(+), 6 deletions(-)
> >
>
> On the principle, the series lgtm.
> Acked-by: David Marchand <david.marchand@redhat.com>
Changed second patch subject to test/event: add driver selftests to
driver-tests suite
Series applied to dpdk-next-net-eventdev/for-main. Thanks
>
>
> --
> David Marchand
>
prev parent reply other threads:[~2023-10-03 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 15:14 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
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 [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='CALBAE1M=ZXT-LO_VibQMaBMyAkgW10oP7w5Zk2W70pcykrzdxQ@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.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).