DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vivek Kumar Sharma <viveksharma@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "intoviveksharma@gmail.com" <intoviveksharma@gmail.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ethdev: use correct QinQ offload flag
Date: Sun, 29 Sep 2019 04:29:05 +0000	[thread overview]
Message-ID: <CY4PR18MB1144772FBBF435CA8EA2728CBB830@CY4PR18MB1144.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1568373289-5629-1-git-send-email-viveksharma@marvell.com>

Ping!


Thanks,
Vivek

________________________________________
From: viveksharma@marvell.com <viveksharma@marvell.com>
Sent: 13 September 2019 16:44
To: dev@dpdk.org
Cc: intoviveksharma@gmail.com; Vivek Kumar Sharma; stable@dpdk.org
Subject: [PATCH] ethdev: use correct QinQ offload flag

From: Vivek Sharma <viveksharma@marvell.com>

Use correct flag for indicating QinQ strip rx offload.

Fixes: dfebfc9882fb ("ethdev: support dynamic configuration of QinQ strip")
Cc: stable@dpdk.org

Signed-off-by: Vivek Sharma <viveksharma@marvell.com>
---
 lib/librte_ethdev/rte_ethdev.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/librte_ethdev/rte_ethdev.c b/lib/librte_ethdev/rte_ethdev.c
index 17d183e..bfc0468 100644
--- a/lib/librte_ethdev/rte_ethdev.c
+++ b/lib/librte_ethdev/rte_ethdev.c
@@ -2823,7 +2823,7 @@ rte_eth_dev_get_vlan_offload(uint16_t port_id)
                ret |= ETH_VLAN_EXTEND_OFFLOAD;

        if (*dev_offloads & DEV_RX_OFFLOAD_QINQ_STRIP)
-               ret |= DEV_RX_OFFLOAD_QINQ_STRIP;
+               ret |= ETH_QINQ_STRIP_OFFLOAD;

        return ret;
 }
--
2.7.4


  reply	other threads:[~2019-09-29  4:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13 11:14 viveksharma
2019-09-29  4:29 ` Vivek Kumar Sharma [this message]
2019-09-29 11:43   ` Andrew Rybchenko
2019-10-09  8:48     ` [dpdk-dev] [dpdk-stable] " 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=CY4PR18MB1144772FBBF435CA8EA2728CBB830@CY4PR18MB1144.namprd18.prod.outlook.com \
    --to=viveksharma@marvell.com \
    --cc=dev@dpdk.org \
    --cc=intoviveksharma@gmail.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).