From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
"Dai, Wei" <wei.dai@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] ethdev: moved bypass functions to ixgbe pmd
Date: Thu, 1 Jun 2017 12:26:49 +0100 [thread overview]
Message-ID: <a2c8bf2f-f023-d19a-5c7c-8dbe19c46b22@intel.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09093B5C9707@shsmsx102.ccr.corp.intel.com>
On 6/1/2017 1:49 AM, Lu, Wenzhuo wrote:
> Hi,
>
>> -----Original Message-----
>> From: Nicolau, Radu
>> Sent: Wednesday, May 31, 2017 7:10 PM
>> To: dev@dpdk.org
>> Cc: Yigit, Ferruh; Iremonger, Bernard; Dai, Wei; Lu, Wenzhuo; Nicolau, Radu
>> Subject: [PATCH v3] ethdev: moved bypass functions to ixgbe pmd
>>
>> Moved all bypass functions to ixgbe pmd and removed function pointers
>> from the eth_dev_ops struct.
>>
>> Changes in v2:
>> CONFIG_RTE_NIC_BYPASS removed, new option in the IXGBE section added,
>> CONFIG_RTE_LIBRTE_IXGBE_BYPASS.
>> Updated test-pmd to always include the bypass commands.
>>
>> Changes in v3:
>> Added is_ixgbe_supported check on all bypass API functions.
>>
>> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-06-01 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 14:30 [dpdk-dev] [PATCH] " Radu Nicolau
2017-05-29 10:38 ` Ferruh Yigit
2017-05-29 15:22 ` [dpdk-dev] [PATCH v2] " Radu Nicolau
2017-05-31 3:29 ` Lu, Wenzhuo
2017-05-31 7:41 ` Dai, Wei
2017-05-31 11:10 ` [dpdk-dev] [PATCH v3] " Radu Nicolau
2017-06-01 0:49 ` Lu, Wenzhuo
2017-06-01 11:26 ` 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=a2c8bf2f-f023-d19a-5c7c-8dbe19c46b22@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=radu.nicolau@intel.com \
--cc=wei.dai@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).