DPDK patches and discussions
 help / color / mirror / Atom feed
From: Harman Kalra <hkalra@marvell.com>
To: <skori@marvell.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/octeontx: fix max Rx packet length corruption
Date: Fri, 29 Jan 2021 00:46:15 +0530	[thread overview]
Message-ID: <20210128191614.GA59457@outlook.office365.com> (raw)
In-Reply-To: <20210126085244.1617026-1-skori@marvell.com>

On Tue, Jan 26, 2021 at 02:22:43PM +0530, skori@marvell.com wrote:
> From: Sunil Kumar Kori <skori@marvell.com>
> 
> Maximum Rx packet length is getting updated twice which
> corrupts actual value.
> 
> Fixes: 3151e6a687a3 ("net/octeontx: support MTU")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Sunil Kumar Kori <skori@marvell.com>

Thanks for fixing.

Acked-by: Harman Kalra <hkalra@marvell.com>

> ---
>  drivers/net/octeontx/octeontx_ethdev.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/net/octeontx/octeontx_ethdev.c b/drivers/net/octeontx/octeontx_ethdev.c
> index 81779885d..5836dbe09 100644
> --- a/drivers/net/octeontx/octeontx_ethdev.c
> +++ b/drivers/net/octeontx/octeontx_ethdev.c
> @@ -867,7 +867,6 @@ octeontx_dev_info(struct rte_eth_dev *dev,
>  
>  	dev_info->max_mac_addrs =
>  				octeontx_bgx_port_mac_entries_get(nic->port_id);
> -	dev_info->max_rx_pktlen = PKI_MAX_PKTLEN;
>  	dev_info->max_rx_queues = 1;
>  	dev_info->max_tx_queues = PKO_MAX_NUM_DQ;
>  	dev_info->min_rx_bufsize = 0;
> -- 
> 2.25.1
> 

  reply	other threads:[~2021-01-28 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26  8:52 skori
2021-01-28 19:16 ` Harman Kalra [this message]
2021-02-04 11:00   ` Jerin Jacob

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=20210128191614.GA59457@outlook.office365.com \
    --to=hkalra@marvell.com \
    --cc=dev@dpdk.org \
    --cc=skori@marvell.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).