patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Dai, Wei" <wei.dai@intel.com>
Cc: dev@dpdk.org, "Ananyev,
	Konstantin" <konstantin.ananyev@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] examples/ip_fragmentation: fix check of packet type
Date: Tue, 04 Apr 2017 14:43:14 +0200	[thread overview]
Message-ID: <1665565.MDcVzfXV8f@xps13> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772583FACFA4A@IRSMSX109.ger.corp.intel.com>

2017-03-15 12:23, Ananyev, Konstantin:
> 
> > -----Original Message-----
> > From: Dai, Wei
> > Sent: Tuesday, March 14, 2017 2:48 PM
> > To: dev@dpdk.org
> > Cc: Ananyev, Konstantin <konstantin.ananyev@intel.com>; Dai, Wei <wei.dai@intel.com>; stable@dpdk.org
> > Subject: [PATCH v2] examples/ip_fragmentation: fix check of packet type
> > 
> > The packet_type in mbuf is not correctly filled by ixgbe 82599 NIC.
> > To use the ether_type in ethernet header to check packet type is
> > more reliaber.
> > 
> > Fixes: 3c0184cc0c60 ("examples: replace some offload flags with packet type")
> > Fixes: ab351fe1c95c ("mbuf: remove packet type from offload flags")
> > 
> > Cc: stable@dpdk.org
> > 
> > Reported-by: Fangfang Wei <fangfangx.wei@intel.com>
> > Signed-off-by: Wei Dai <wei.dai@intel.com>
> > ---
> 
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>

Applied, thanks

      reply	other threads:[~2017-04-04 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 14:47 [dpdk-stable] " Wei Dai
     [not found] ` <49759EB36A64CF4892C1AFEC9231E8D64E50CCDD@PGSMSX101.gar.corp.intel.com>
2017-03-15  2:42   ` [dpdk-stable] FW: " Wei, FangfangX
2017-03-15 12:23 ` [dpdk-stable] " Ananyev, Konstantin
2017-04-04 12:43   ` Thomas Monjalon [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=1665565.MDcVzfXV8f@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=stable@dpdk.org \
    --cc=wei.dai@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).