DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiao Wang <xiao.w.wang@intel.com>, qi.z.zhang@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/fm10k: fix VLAN strip offload flag
Date: Wed, 27 Mar 2019 15:24:23 +0000	[thread overview]
Message-ID: <04e5403d-ba19-84aa-e148-affb6dd3c254@intel.com> (raw)
Message-ID: <20190327152423.tDwMEgjZOQwGp6-vgI3JIjAhtonKpqL2fVFVexGElFg@z> (raw)
In-Reply-To: <20190327050903.170388-1-xiao.w.wang@intel.com>

On 3/27/2019 5:09 AM, Xiao Wang wrote:
> Since the VLAN header is stripped from mbuf data, PKT_RX_VLAN_STRIPPED
> should be set in offload flag.
> 
> Fixes: 6b59a3bc82b1 ("fm10k: fix VLAN in Rx mbuf")
> Fixes: 7092be8437bd ("fm10k: add vector Rx")
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>

Applied to dpdk-next-net/master, thanks.

  parent reply	other threads:[~2019-03-27 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27  5:09 Xiao Wang
2019-03-27  5:09 ` Xiao Wang
2019-03-27 15:24 ` Ferruh Yigit [this message]
2019-03-27 15:24   ` 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=04e5403d-ba19-84aa-e148-affb6dd3c254@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=stable@dpdk.org \
    --cc=xiao.w.wang@intel.com \
    /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).