DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Wu, Yanglong" <yanglong.wu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Dai, Wei" <wei.dai@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: fix missing VLAN offload capability
Date: Fri, 11 May 2018 02:53:06 +0100	[thread overview]
Message-ID: <11095a5b-b98f-af46-0b83-12ce0a12ba1a@intel.com> (raw)
In-Reply-To: <039ED4275CED7440929022BC67E70611531B0F83@SHSMSX103.ccr.corp.intel.com>

On 5/11/2018 2:35 AM, Zhang, Qi Z wrote:
> Hi Yanglong
> 	The patch is OK, could you rebase to dpdk-next-net ? 
> Thanks
> Qi
> 
>> -----Original Message-----
>> From: Wu, Yanglong
>> Sent: Thursday, May 10, 2018 2:51 PM
>> To: dev@dpdk.org
>> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Dai, Wei <wei.dai@intel.com>; Wu,
>> Yanglong <yanglong.wu@intel.com>
>> Subject: [PATCH v2] net/i40e: fix missing VLAN offload capability
>>
>> VLAN offload capability should be exposed in VF since i40e does support it.
>>
>> Fixes: c3ac7c5b0b8a ("net/i40e: convert to new Rx offloads API")
>> Signed-off-by: Yanglong Wu <yanglong.wu@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

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

      reply	other threads:[~2018-05-11  1:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10  2:45 [dpdk-dev] [PATCH] " Yanglong Wu
2018-05-10  3:06 ` Zhang, Qi Z
2018-05-10  4:57 ` [dpdk-dev] [PATCH v2] " Yanglong Wu
2018-05-10  6:50 ` Yanglong Wu
2018-05-11  1:35   ` Zhang, Qi Z
2018-05-11  1:53     ` Ferruh Yigit [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=11095a5b-b98f-af46-0b83-12ce0a12ba1a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=wei.dai@intel.com \
    --cc=yanglong.wu@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).