DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>,
	Remy Horton <remy.horton@intel.com>,
	dev@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Beilei Xing <beilei.xing@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] net/ixgbe: fix missing Port Representor data-path
Date: Fri, 11 May 2018 17:08:27 +0100	[thread overview]
Message-ID: <f0ef6bcd-0a89-c532-f35d-ca4e1fcecf75@intel.com> (raw)
In-Reply-To: <63206320-74f2-f36e-b0ac-dd60373ee9ef@intel.com>

On 5/11/2018 3:04 PM, Mohammad Abdul Awal wrote:
> 
> 
> On 11/05/2018 13:28, Remy Horton wrote:
>> This patch adds Rx and Tx burst functions to the ixgbe
>> Port Representors, so that the implementation within
>> ixgbe PMD can be tested using applications such as
>> testpmd which require data-path functionality.
>>
>> Fixes: cf80ba6e2038 ("net/ixgbe: add support for representor ports")
>>
>> Signed-off-by: Remy Horton <remy.horton@intel.com>

> Acked-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>

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

      reply	other threads:[~2018-05-11 16:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 15:00 [dpdk-dev] [PATCH] net/i40e: fix missing Port Representor data-path callbacks Remy Horton
2018-05-11 10:48 ` Mohammad Abdul Awal
2018-05-11 12:29   ` Remy Horton
2018-05-11 12:28 ` [dpdk-dev] [PATCH v2 0/2] " Remy Horton
2018-05-11 12:28   ` [dpdk-dev] [PATCH v2 1/2] net/i40e: fix missing Port Representor data-path Remy Horton
2018-05-11 14:04     ` Mohammad Abdul Awal
2018-05-11 16:08       ` Ferruh Yigit
2018-05-11 12:28   ` [dpdk-dev] [PATCH v2 2/2] net/ixgbe: " Remy Horton
2018-05-11 14:04     ` Mohammad Abdul Awal
2018-05-11 16:08       ` 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=f0ef6bcd-0a89-c532-f35d-ca4e1fcecf75@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=mohammad.abdul.awal@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=remy.horton@intel.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).