DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Xing, Beilei" <beilei.xing@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add limitations for i40e PMD
Date: Wed, 12 Oct 2016 16:17:44 +0100	[thread overview]
Message-ID: <20161012151744.GB104428@bricha3-MOBL3> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2026266D2@IRSMSX103.ger.corp.intel.com>

On Fri, Sep 30, 2016 at 03:09:53PM +0000, Mcnamara, John wrote:
> 
> 
> > -----Original Message-----
> > From: Wu, Jingjing
> > Sent: Friday, September 30, 2016 7:46 AM
> > To: dev@dpdk.org
> > Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei
> > <beilei.xing@intel.com>; Mcnamara, John <john.mcnamara@intel.com>
> > Subject: [PATCH v3] doc: add limitations for i40e PMD
> > 
> > This patch adds "Limitations or Known issues" section for i40e PMD,
> > including two items:
> > 1. MPLS packet classification on X710/XL710 2. 16 Byte Descriptor cannot
> > be used on DPDK VF 3. Link down with i40e kernel driver after DPDK
> > application exist
> > 
> > Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>
> 
> 
> Acked-by: John McNamara <john.mcnamara@intel.com>
> 
Applied to dpdk-next-net/rel_16_11

/Bruce

      reply	other threads:[~2016-10-12 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06  2:17 [dpdk-dev] [PATCH] " Jingjing Wu
2016-09-13  9:48 ` Xing, Beilei
2016-09-16 17:06 ` [dpdk-dev] [PATCH v2] " Jingjing Wu
2016-09-26 15:32   ` Mcnamara, John
2016-09-30  6:46   ` [dpdk-dev] [PATCH v3] " Jingjing Wu
2016-09-30 15:09     ` Mcnamara, John
2016-10-12 15:17       ` Bruce Richardson [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=20161012151744.GB104428@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=john.mcnamara@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).