DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xiao, QimaiX" <qimaix.xiao@intel.com>
To: "Xia, Chenbo" <chenbo.xia@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
	"somnath.kotur@broadcom.com" <somnath.kotur@broadcom.com>,
	"kishore.padmanabha@broadcom.com"
	<kishore.padmanabha@broadcom.com>,
	"venkatkumar.duvvuru@broadcom.com"
	<venkatkumar.duvvuru@broadcom.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix variable size of port id
Date: Thu, 3 Sep 2020 06:49:37 +0000	[thread overview]
Message-ID: <MWHPR1101MB2254A6923F8066F86A7CDF05FB2C0@MWHPR1101MB2254.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200804174147.64473-1-chenbo.xia@intel.com>

Tested-by: Xiao, Qimai <qimaix.xiao@intel.com>

Regards,
Xiao Qimai

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Chenbo Xia
> Sent: Wednesday, August 5, 2020 1:42 AM
> To: dev@dpdk.org
> Cc: ajit.khaparde@broadcom.com; somnath.kotur@broadcom.com;
> kishore.padmanabha@broadcom.com;
> venkatkumar.duvvuru@broadcom.com; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH] net/bnxt: fix variable size of port id
> 
> Currenly the variable size of ethdev port id is 8 bits. This patch standarizes it
> to 16 bits.
> 
> Fixes: 769de16872ab ("net/bnxt: fix port default rule create/destroy")
> Cc: stable@dpdk.org
> 
> Reported-by: Yinan Wang <yinan.wang@intel.com>
> Signed-off-by: Chenbo Xia <chenbo.xia@intel.com>
> ---
>  drivers/net/bnxt/tf_ulp/ulp_def_rules.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/bnxt/tf_ulp/ulp_def_rules.c
> b/drivers/net/bnxt/tf_ulp/ulp_def_rules.c
> index 9fb1a028f..ff5aed3d7 100644
> --- a/drivers/net/bnxt/tf_ulp/ulp_def_rules.c
> +++ b/drivers/net/bnxt/tf_ulp/ulp_def_rules.c
> @@ -397,7 +397,7 @@ void
>  bnxt_ulp_destroy_df_rules(struct bnxt *bp, bool global)  {
>  	struct bnxt_ulp_df_rule_info *info;
> -	uint8_t port_id;
> +	uint16_t port_id;
> 
>  	if (!BNXT_TRUFLOW_EN(bp) ||
>  	    BNXT_ETH_DEV_IS_REPRESENTOR(bp->eth_dev))
> --
> 2.17.1


  parent reply	other threads:[~2020-09-03  6:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04 17:41 Chenbo Xia
2020-08-04 16:22 ` Stephen Hemminger
2020-08-05 20:18 ` Thomas Monjalon
2020-08-06  2:03   ` Xia, Chenbo
2020-08-06  7:57     ` Thomas Monjalon
2020-09-03  6:49 ` Xiao, QimaiX [this message]
2020-09-25  5:37 ` [dpdk-dev] [PATCH v2 1/3] net: fix variable size of ethdev " Chenbo Xia
2020-09-25  5:37   ` [dpdk-dev] [PATCH v2 2/3] app: " Chenbo Xia
2020-09-25  5:37   ` [dpdk-dev] [PATCH v2 3/3] doc: " Chenbo Xia
2020-09-29 18:51   ` [dpdk-dev] [PATCH v2 1/3] net: " Ed Czeck
2020-09-30  4:23   ` [dpdk-dev] [PATCH v3 " Chenbo Xia
2020-09-30  4:23     ` [dpdk-dev] [PATCH v3 2/3] app: " Chenbo Xia
2020-09-30  4:23     ` [dpdk-dev] [PATCH v3 3/3] doc: " Chenbo Xia
2020-09-30 13:40     ` [dpdk-dev] [PATCH v3 1/3] net: " Ajit Khaparde
2020-09-30 17:13     ` 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=MWHPR1101MB2254A6923F8066F86A7CDF05FB2C0@MWHPR1101MB2254.namprd11.prod.outlook.com \
    --to=qimaix.xiao@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=kishore.padmanabha@broadcom.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=venkatkumar.duvvuru@broadcom.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).