From: beilei.xing@intel.com
To: qi.z.zhang@intel.com
Cc: dev@dpdk.org, Jingjing Wu <jingjing.wu@intel.com>,
stable@dpdk.org, Beilei Xing <beilei.xing@intel.com>
Subject: [PATCH v2 4/5] net/idpf: fix driver init symbols
Date: Fri, 6 Jan 2023 09:05:00 +0000 [thread overview]
Message-ID: <20230106090501.9106-5-beilei.xing@intel.com> (raw)
In-Reply-To: <20230106090501.9106-1-beilei.xing@intel.com>
From: Jingjing Wu <jingjing.wu@intel.com>
This patch fixes idpf driver init symbols.
Fixes: 549343c25db8 ("net/idpf: support device initialization")
Cc: stable@dpdk.org
Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>
Signed-off-by: Beilei Xing <beilei.xing@intel.com>
---
drivers/net/idpf/idpf_ethdev.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/net/idpf/idpf_ethdev.c b/drivers/net/idpf/idpf_ethdev.c
index f7b3f8f515..89af27ca34 100644
--- a/drivers/net/idpf/idpf_ethdev.c
+++ b/drivers/net/idpf/idpf_ethdev.c
@@ -1251,7 +1251,11 @@ static struct rte_pci_driver rte_idpf_pmd = {
*/
RTE_PMD_REGISTER_PCI(net_idpf, rte_idpf_pmd);
RTE_PMD_REGISTER_PCI_TABLE(net_idpf, pci_id_idpf_map);
-RTE_PMD_REGISTER_KMOD_DEP(net_ice, "* igb_uio | uio_pci_generic | vfio-pci");
+RTE_PMD_REGISTER_KMOD_DEP(net_idpf, "* igb_uio | vfio-pci");
+RTE_PMD_REGISTER_PARAM_STRING(net_idpf,
+ IDPF_TX_SINGLE_Q "=<0|1> "
+ IDPF_RX_SINGLE_Q "=<0|1> "
+ IDPF_VPORT "=[vport_set0,[vport_set1],...]");
RTE_LOG_REGISTER_SUFFIX(idpf_logtype_init, init, NOTICE);
RTE_LOG_REGISTER_SUFFIX(idpf_logtype_driver, driver, NOTICE);
--
2.26.2
prev parent reply other threads:[~2023-01-06 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221208072725.32434-1-beilei.xing@intel.com>
2022-12-08 7:27 ` [PATCH 3/3] net/idpf: fix splitq xmit free beilei.xing
[not found] ` <20230106090501.9106-1-beilei.xing@intel.com>
2023-01-06 9:04 ` [PATCH v2 3/5] " beilei.xing
2023-01-06 9:05 ` beilei.xing [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=20230106090501.9106-5-beilei.xing@intel.com \
--to=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@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).