DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Harman Kalra <hkalra@marvell.com>, Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
	 Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/octeontx2: fix get supported ptype callback
Date: Mon, 13 Jan 2020 15:01:19 +0530	[thread overview]
Message-ID: <CALBAE1PnrhtjGroG+UVfmGeLkJcmQEOBrrpw6FnGZ1F9DSYFbQ@mail.gmail.com> (raw)
In-Reply-To: <1576173504-29467-1-git-send-email-hkalra@marvell.com>

On Thu, Dec 12, 2019 at 11:29 PM Harman Kalra <hkalra@marvell.com> wrote:
>
> Setting up supported ptypes using testpmd command is failing
> because supported_ptypes_get callback will never return ptypes
> supported, as NIX_RX_OFFLOAD_PTYPE_F bit in rx_offload_flags
> is zero by default in testpmd.
>
> Fixes: d2706e15e6fb ("net/octeontx2: support reduced set of packet types")
> Cc: stable@dpdk.org
>
> Signed-off-by: Harman Kalra <hkalra@marvell.com>


Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-mrvl/master. Thanks

> ---
>  drivers/net/octeontx2/otx2_lookup.c | 7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/octeontx2/otx2_lookup.c b/drivers/net/octeontx2/otx2_lookup.c
> index bcf2ff4e8..568557116 100644
> --- a/drivers/net/octeontx2/otx2_lookup.c
> +++ b/drivers/net/octeontx2/otx2_lookup.c
> @@ -17,7 +17,7 @@
>  const uint32_t *
>  otx2_nix_supported_ptypes_get(struct rte_eth_dev *eth_dev)
>  {
> -       struct otx2_eth_dev *dev = otx2_eth_pmd_priv(eth_dev);
> +       RTE_SET_USED(eth_dev);
>
>         static const uint32_t ptypes[] = {
>                 RTE_PTYPE_L2_ETHER_QINQ, /* LB */
> @@ -56,10 +56,7 @@ otx2_nix_supported_ptypes_get(struct rte_eth_dev *eth_dev)
>                 RTE_PTYPE_UNKNOWN,
>         };
>
> -       if (dev->rx_offload_flags & NIX_RX_OFFLOAD_PTYPE_F)
> -               return ptypes;
> -       else
> -               return NULL;
> +       return ptypes;
>  }
>
>  int
> --
> 2.18.0
>

      reply	other threads:[~2020-01-13  9:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 17:58 Harman Kalra
2020-01-13  9:31 ` 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=CALBAE1PnrhtjGroG+UVfmGeLkJcmQEOBrrpw6FnGZ1F9DSYFbQ@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@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).