From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Nikhil Rao <nikhil.rao@intel.com>
Cc: dev@dpdk.org, vipin.varghese@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 1/2] test/event: fix eth Rx adapter autotest for skeleton PMD
Date: Mon, 1 Oct 2018 15:39:41 +0530 [thread overview]
Message-ID: <20181001100939.GA29705@jerin> (raw)
In-Reply-To: <1537859945-16759-1-git-send-email-nikhil.rao@intel.com>
-----Original Message-----
> Date: Tue, 25 Sep 2018 12:49:04 +0530
> From: Nikhil Rao <nikhil.rao@intel.com>
> To: jerin.jacob@caviumnetworks.com
> CC: dev@dpdk.org, Nikhil Rao <nikhil.rao@intel.com>,
> vipin.varghese@intel.com, stable@dpdk.org
> Subject: [PATCH v3 1/2] test/event: fix eth Rx adapter autotest for
> skeleton PMD
> X-Mailer: git-send-email 1.8.3.1
>
>
> skeleton PMD does not support
> RTE_EVENT_ETH_RX_ADAPTER_CAP_MULTI_EVENTQ and
> implicit_release_disable so make the Rx queue_id = -1 and
> initialize the event port configuration to zero.
>
> Fixes: ec36d881f56d ("eventdev: add implicit release disable capability")
> Fixes: 2a9c83ae3b2e ("test/eventdev: add multi-ports test")
> Cc: vipin.varghese@intel.com
> CC: stable@dpdk.org
>
> Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
Series applied to dpdk-next-eventdev/master. Thanks.
prev parent reply other threads:[~2018-10-01 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 12:03 [dpdk-dev] [PATCH] " Nikhil Rao
2018-09-05 13:51 ` [dpdk-dev] [PATCH v2 1/2] " Nikhil Rao
2018-09-05 13:51 ` [dpdk-dev] [PATCH v2 2/2] test/event: fix Rx adapter intr " Nikhil Rao
2018-09-10 13:44 ` [dpdk-dev] [PATCH v2 1/2] test/event: fix eth Rx adapter " Jerin Jacob
2018-09-25 7:19 ` [dpdk-dev] [PATCH v3 " Nikhil Rao
2018-09-25 7:19 ` [dpdk-dev] [PATCH v3 2/2] test/event: fix Rx adapter intr " Nikhil Rao
2018-09-29 12:00 ` Jerin Jacob
2018-09-29 11:59 ` [dpdk-dev] [PATCH v3 1/2] test/event: fix eth Rx adapter " Jerin Jacob
2018-10-01 10:09 ` 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=20181001100939.GA29705@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=nikhil.rao@intel.com \
--cc=stable@dpdk.org \
--cc=vipin.varghese@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 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).