patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>,
	dpdk-dev <dev@dpdk.org>,  dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/bnxt: fix ptype index calculation
Date: Wed, 20 Jan 2021 23:11:43 -0800	[thread overview]
Message-ID: <CACZ4nhtS0-5Uf8NV_mMtS5=A9CkR8nJRxffecX_a8z5Zob5cig@mail.gmail.com> (raw)
In-Reply-To: <20210118215709.4720-1-lance.richardson@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

On Mon, Jan 18, 2021 at 1:57 PM Lance Richardson
<lance.richardson@broadcom.com> wrote:
>
> Fix mask to include all four bits of hardware packet type
> field.
>
> Fixes: 97b1db288dd0 ("net/bnxt: use table based packet type translation")
> Cc: stable@dpdk.org
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
Patch applied to dpdk-next-net-brcm.

> ---
>  drivers/net/bnxt/bnxt_rxr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/bnxt/bnxt_rxr.c b/drivers/net/bnxt/bnxt_rxr.c
> index a195bf1187..969cae19fc 100644
> --- a/drivers/net/bnxt/bnxt_rxr.c
> +++ b/drivers/net/bnxt/bnxt_rxr.c
> @@ -402,7 +402,7 @@ bnxt_init_ptype_table(void)
>
>                 ip6 = i & (RX_PKT_CMPL_FLAGS2_IP_TYPE >> 7);
>                 tun = i & (RX_PKT_CMPL_FLAGS2_T_IP_CS_CALC >> 2);
> -               type = (i & 0x38) << 9;
> +               type = (i & 0x78) << 9;
>
>                 if (!tun && !ip6)
>                         l3 = RTE_PTYPE_L3_IPV4_EXT_UNKNOWN;
> --
> 2.25.1
>

      reply	other threads:[~2021-01-21  7:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 21:57 Lance Richardson
2021-01-21  7:11 ` Ajit Khaparde [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='CACZ4nhtS0-5Uf8NV_mMtS5=A9CkR8nJRxffecX_a8z5Zob5cig@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=lance.richardson@broadcom.com \
    --cc=somnath.kotur@broadcom.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).