From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@caviumnetworks.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] test/eventdev: use CPU event type
Date: Sat, 9 Dec 2017 14:57:47 +0530 [thread overview]
Message-ID: <20171209092746.GC13525@jerin> (raw)
In-Reply-To: <20171204084444.7awnhs2rz2wmblt7@Pavan-LT>
-----Original Message-----
> Date: Mon, 4 Dec 2017 14:14:45 +0530
> From: Pavan Nikhilesh Bhagavatula <pbhagavatula@caviumnetworks.com>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] test/eventdev: use CPU event type
> User-Agent: NeoMutt/20170609 (1.8.3)
>
> On Mon, Dec 04, 2017 at 01:41:18PM +0530, Jerin Jacob wrote:
> > octeontx test application was using non RTE_EVENT_TYPE_CPU
> > event type to generate the event from CPU. Upon the introduction
> > of ethdev Rx adapter, RTE_EVENT_TYPE_ETHDEV has special
> > meaning. So avoid using non RTE_EVENT_TYPE_CPU event types
> > to inject events from CPU.
> >
> > Fixes: d0d654986018 ("net/octeontx: support event Rx adapter")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> > ---
> > test/test/test_eventdev_octeontx.c | 6 +++---
> Reviewed-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Applied to dpdk-next-eventdev/master. Thanks.
prev parent reply other threads:[~2017-12-09 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 8:11 [PATCH] test/eventdev: use CPU event type Jerin Jacob
2017-12-04 8:44 ` Pavan Nikhilesh Bhagavatula
2017-12-09 9:27 ` 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=20171209092746.GC13525@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=pbhagavatula@caviumnetworks.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.