From: Jerin Jacob <jerinjacobk@gmail.com> To: Harman Kalra <hkalra@marvell.com>, Ferruh Yigit <ferruh.yigit@intel.com> Cc: Sunil Kumar Kori <skori@marvell.com>, dpdk-dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org> Subject: Re: [dpdk-dev] [PATCH] net/octeontx: fix max Rx packet length corruption Date: Thu, 4 Feb 2021 16:30:58 +0530 Message-ID: <CALBAE1P_ZnT1x2WM5jXC_T-Fc98rnY=A3tUntoaAxuEe3oLp9g@mail.gmail.com> (raw) In-Reply-To: <20210128191614.GA59457@outlook.office365.com> On Fri, Jan 29, 2021 at 12:46 AM Harman Kalra <hkalra@marvell.com> wrote: > > 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> Applied to dpdk-next-net-mrvl/for-main. Thanks > > > --- > > 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 > >
prev parent reply other threads:[~2021-02-04 11:01 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 2021-02-04 11:00 ` Jerin Jacob [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='CALBAE1P_ZnT1x2WM5jXC_T-Fc98rnY=A3tUntoaAxuEe3oLp9g@mail.gmail.com' \ --to=jerinjacobk@gmail.com \ --cc=dev@dpdk.org \ --cc=ferruh.yigit@intel.com \ --cc=hkalra@marvell.com \ --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
DPDK patches and discussions This inbox may be cloned and mirrored by anyone: git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \ dev@dpdk.org public-inbox-index dev Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git