DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: Shweta Choudaha <shweta.choudaha@gmail.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"shweta.choudaha@att.com" <shweta.choudaha@att.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/ixgbe: Add API to update SBP bit
Date: Tue, 8 May 2018 01:47:01 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E71AEA808F@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20180410154246.102440-1-shweta.choudaha@gmail.com>



> -----Original Message-----
> From: Shweta Choudaha [mailto:shweta.choudaha@gmail.com]
> Sent: Tuesday, April 10, 2018 11:43 PM
> To: dev@dpdk.org
> Cc: Lu, Wenzhuo; Ananyev, Konstantin; Zhang, Helin; Yigit, Ferruh;
> shweta.choudaha@att.com
> Subject: [PATCH v2] net/ixgbe: Add API to update SBP bit
> 
> From: Shweta Choudaha <shweta.choudaha@att.com>
> 
> Add ixgbe API to enable SBP bit in FCTRL register to allow receiving packets that
> may otherwise be considered length errors by ixgbe and dropped
> 
> Signed-off-by: Shweta Choudaha <shweta.choudaha@att.com>
> Reviewed-by: Chas Williams <chas3@att.com>
> Reviewed-by: Luca Boccassi <bluca@debian.org>
Applied to dpdk-next-net-intel, thanks!

/Helin

      reply	other threads:[~2018-05-08  1:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23 11:59 [dpdk-dev] [PATCH 0/1] " Shweta Choudaha
2018-02-23 11:59 ` [dpdk-dev] [PATCH 1/1] " Shweta Choudaha
2018-04-04  2:25   ` Lu, Wenzhuo
2018-04-04 10:14     ` Ferruh Yigit
2018-04-04 10:40       ` Bruce Richardson
2018-04-10 15:58         ` Shweta Choudaha
2018-04-26 10:20           ` Shweta Choudaha
2018-04-26 10:56             ` Ferruh Yigit
2018-05-01 22:15               ` Shweta Choudaha
2018-04-10 15:42   ` [dpdk-dev] [PATCH v2] " Shweta Choudaha
2018-05-08  1:47     ` Zhang, Helin [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=F35DEAC7BCE34641BA9FAC6BCA4A12E71AEA808F@SHSMSX103.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=shweta.choudaha@att.com \
    --cc=shweta.choudaha@gmail.com \
    --cc=wenzhuo.lu@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).