From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Liu, Mingxia" <mingxia.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Liu, Mingxia" <mingxia.liu@intel.com>
Subject: RE: [PATCH] net/idpf: refine RTE_PMD_REGISTER_PARAM_STRING of IDPF PMD
Date: Fri, 30 Jun 2023 09:08:15 +0000 [thread overview]
Message-ID: <DM4PR11MB5994E74A757AEFCD34AFC229D72AA@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230626140626.490896-1-mingxia.liu@intel.com>
> -----Original Message-----
> From: Mingxia Liu <mingxia.liu@intel.com>
> Sent: Monday, June 26, 2023 10:06 PM
> To: dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>;
> Liu, Mingxia <mingxia.liu@intel.com>
> Subject: [PATCH] net/idpf: refine RTE_PMD_REGISTER_PARAM_STRING of IDPF
> PMD
No need to mention the PMD in the title as its duplicate with the prefix.
How about
net/idpf: refine vport parameter string
>
> This patch refines 'IDPF_VPORT' param string in
> 'RTE_PMD_REGISTER_PARAM_STRING'.
>
> Signed-off-by: Mingxia Liu <mingxia.liu@intel.com>
> ---
> drivers/net/idpf/idpf_ethdev.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/idpf/idpf_ethdev.c b/drivers/net/idpf/idpf_ethdev.c
> index 3e66898aaf..34ca5909f1 100644
> --- a/drivers/net/idpf/idpf_ethdev.c
> +++ b/drivers/net/idpf/idpf_ethdev.c
> @@ -1478,9 +1478,9 @@ 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_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],...]");
> + IDPF_TX_SINGLE_Q "=<0|1> "
> + IDPF_RX_SINGLE_Q "=<0|1> "
> + IDPF_VPORT
> +"=[vport0_begin[-vport0_end][,vport1_begin[-vport1_end]][,..]]");
Better to use "<>" to wrap a symbol
How about " [<begin>[-<end>][,<begin >[-<end>]][, ... ]]"?
>
> RTE_LOG_REGISTER_SUFFIX(idpf_logtype_init, init, NOTICE);
> RTE_LOG_REGISTER_SUFFIX(idpf_logtype_driver, driver, NOTICE);
> --
> 2.34.1
next prev parent reply other threads:[~2023-06-30 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 14:06 Mingxia Liu
2023-06-30 9:08 ` Zhang, Qi Z [this message]
2023-06-30 10:47 ` Liu, Mingxia
2023-06-30 18:51 ` [PATCH v2] net/idpf: refine vport parameter string Mingxia Liu
2023-07-03 2:25 ` Zhang, Qi Z
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=DM4PR11MB5994E74A757AEFCD34AFC229D72AA@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=mingxia.liu@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).