DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH v2] net/octeontx: fix vdev name
Date: Wed, 13 Mar 2019 14:58:15 -0700	[thread overview]
Message-ID: <20190313215815.19629-1-stephen@networkplumber.org> (raw)
Message-ID: <20190313215815.FDLAyX34eEy3-H-c7norCSe2RD0Qlz8CgBP69bptL9Y@z> (raw)

The octeontx driver is creating vdev with name  "OCTEONTX_PMD"
which is an artifact from how RTE_PMD_REGISTER_VDEV arguments
work.

Change to use the same convention as all the other network
drivers ie "net_octeontx").

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Reviewed-by: Ramil Rosen <ramirose@gmail.com>
---
v2 - fix typo in commit message and name should be net_octeontx
     not net_octeon

 drivers/net/octeontx/octeontx_ethdev.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/net/octeontx/octeontx_ethdev.h b/drivers/net/octeontx/octeontx_ethdev.h
index 920f6f89b882..2a4a08afcc7f 100644
--- a/drivers/net/octeontx/octeontx_ethdev.h
+++ b/drivers/net/octeontx/octeontx_ethdev.h
@@ -21,6 +21,7 @@
 #include "base/octeontx_pkovf.h"
 #include "base/octeontx_io.h"
 
+#define OCTEONTX_PMD				net_octeontx
 #define OCTEONTX_VDEV_DEFAULT_MAX_NR_PORT	12
 #define OCTEONTX_VDEV_NR_PORT_ARG		("nr_port")
 #define OCTEONTX_MAX_NAME_LEN			32
-- 
2.17.1


             reply	other threads:[~2019-03-13 21:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 21:58 Stephen Hemminger [this message]
2019-03-13 21:58 ` Stephen Hemminger
2019-03-14 15:35 ` Jerin Jacob Kollanukkaran
2019-03-14 15:35   ` Jerin Jacob Kollanukkaran
2019-03-19 18:59   ` Ferruh Yigit
2019-03-19 18:59     ` Ferruh Yigit
2019-03-19 22:19     ` Stephen Hemminger
2019-03-19 22:19       ` Stephen Hemminger
2019-03-20 15:09       ` Ferruh Yigit
2019-03-20 15:09         ` Ferruh Yigit

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=20190313215815.19629-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    /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).