DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nipun Gupta <nipun.gupta@nxp.com>
To: thomas@monjalon.net, jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org, santosh.shukla@caviumnetworks.com,
	hemant.agrawal@nxp.com, shreyansh.jain@nxp.com,
	sunil.kori@nxp.com, Nipun Gupta <nipun.gupta@nxp.com>
Subject: [dpdk-dev] [PATCH 3/4] event/dpaa: rename dpaa vdev with dpaa1
Date: Mon,  5 Feb 2018 10:51:56 +0530	[thread overview]
Message-ID: <1517808117-28562-3-git-send-email-nipun.gupta@nxp.com> (raw)
In-Reply-To: <1517808117-28562-1-git-send-email-nipun.gupta@nxp.com>

DPAA2 eventdev is named as event_dpaa2 which conflicts with
event_dpaa when both are compiled in together. So event_dpaa
is required to renamed.

Fixes: 1ee9569576f6 ("config: enable dpaaX drivers for generic ARMv8")

Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
---
 doc/guides/eventdevs/dpaa.rst      | 6 +++---
 drivers/event/dpaa/dpaa_eventdev.h | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/guides/eventdevs/dpaa.rst b/doc/guides/eventdevs/dpaa.rst
index 44ed128..7383295 100644
--- a/doc/guides/eventdevs/dpaa.rst
+++ b/doc/guides/eventdevs/dpaa.rst
@@ -111,16 +111,16 @@ The dpaa eventdev is exposed as a vdev device which consists of a set of channel
 and queues. On EAL initialization, dpaa components will be
 probed and then vdev device can be created from the application code by
 
-* Invoking ``rte_vdev_init("event_dpaa")`` from the application
+* Invoking ``rte_vdev_init("event_dpaa1")`` from the application
 
-* Using ``--vdev="event_dpaa"`` in the EAL options, which will call
+* Using ``--vdev="event_dpaa1"`` in the EAL options, which will call
   rte_vdev_init() internally
 
 Example:
 
 .. code-block:: console
 
-    ./your_eventdev_application --vdev="event_dpaa"
+    ./your_eventdev_application --vdev="event_dpaa1"
 
 Limitations
 -----------
diff --git a/drivers/event/dpaa/dpaa_eventdev.h b/drivers/event/dpaa/dpaa_eventdev.h
index 153f38d..918fe35 100644
--- a/drivers/event/dpaa/dpaa_eventdev.h
+++ b/drivers/event/dpaa/dpaa_eventdev.h
@@ -10,7 +10,7 @@
 #include <rte_atomic.h>
 #include <rte_per_lcore.h>
 
-#define EVENTDEV_NAME_DPAA_PMD		event_dpaa
+#define EVENTDEV_NAME_DPAA_PMD		event_dpaa1
 
 #define EVENTDEV_DRV_LOG(fmt, args...)	\
 		DPAA_EVENTDEV_INFO(fmt, ## args)
-- 
1.9.1

  parent reply	other threads:[~2018-02-05  5:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05  5:21 [dpdk-dev] [PATCH 1/4] bus/fslmc: fix registering dpaa2 mempool ops Nipun Gupta
2018-02-05  5:21 ` [dpdk-dev] [PATCH 2/4] bus/dpaa: fix registering dpaa " Nipun Gupta
2018-02-05  5:36   ` santosh
2018-02-05  6:31   ` Shreyansh Jain
2018-02-05  5:21 ` Nipun Gupta [this message]
2018-02-05 11:56   ` [dpdk-dev] [PATCH 3/4] event/dpaa: rename dpaa vdev with dpaa1 Hemant Agrawal
2018-02-05  5:21 ` [dpdk-dev] [PATCH 4/4] event/dpaa: fix portal allocation Nipun Gupta
2018-02-05 11:53   ` Hemant Agrawal
2018-02-05  6:32 ` [dpdk-dev] [PATCH 1/4] bus/fslmc: fix registering dpaa2 mempool ops Shreyansh Jain
2018-02-05 23:44   ` Thomas Monjalon

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=1517808117-28562-3-git-send-email-nipun.gupta@nxp.com \
    --to=nipun.gupta@nxp.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=santosh.shukla@caviumnetworks.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=sunil.kori@nxp.com \
    --cc=thomas@monjalon.net \
    /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).